postgres: add an extensions
option
#604
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a convenience option to install a list of PostgreSQL extensions. The set of available extensions is provided as an argument.
You could already do this by modifying the package with
withPackages
and then overridingservices.postgres.package
. The new option has two advantages over the existing approach:It's easier to find in the documentation.
Users unfamiliar with nixpkgs are unlikely to be aware of
pkgs.postgresql.withPackages
specifically, or the pattern ingeneral.
The NixOS services calls this option
extraPlugins
. First of all, that's not what PostgreSQL calls them. Second, you have to manually source the extensions frompkgs.postgresql.pkgs
and ensure that the PostgreSQL version matches whatever is specified inservices.postgres.package
.The description for the option contains a list of available extensions generated from the current version of PostgreSQL.