v1.4.3

Fixes a problem in building release candidate versions of PostgreSQL (18rc1).

v1.4.2

Fix a bug in building beta releases with major numbers greater than 17.

v1.4.0

What's Changed

• Merge configs from least to most specific by @theory in #88

Full Changelog: v1.3.9...v1.4.0

v1.3.9

This version provides support for multiple configuration files, so that a per-major release file can be used to configure all of the PostgreSQL instances that have the same major release and do not have a specific configuration file.

v1.3.8

This release fixes an issue building Postgres 17 without DocBook tools (#79). It also makes dependency check messages more descriptive (#76).

v1.3.7

This release allows pgenv to handle (i.e., start, stop and so on) externally managed PostgreSSQL versions.
An externally managed PostgreSQL version is a folder within PGENV_ROOT that is named with pgsql-xxx (where xxx can be anything the user wants) and has the same structure as any other PostgreSQL installation.

v1.3.6

Adds the PGENV_SCRIPT_FIRSTSTART that allows the run of an executable custom script to initialize the cluster at its very first start.
The script is run only once.

v1.3.5

This release fixes a bug in the invocation of the post-initdb custom script.

v1.3.3

This release adds two new environment variables:

• PGENV_WRITE_CONFIGURATION_FILE_AUTOMATICALLY that, if set to a false value (e.g., 0) prevents pgenv to write a configuration file (or overwrite an existing one) after a build or rebuild;
• PGENV_CONFIGURATION_FILE that can be used to force pgenv to use a custom configuration file instead of let it guess the correct file to use depending on the PostgreSQL version to work with.

The new subcommand config path has been added: it allows the user to get information about which exact configuration file path will be used from subsequent commands.

Removed typos in documentation and debug output.

v1.3.2

This is a maintenance release.
A bug in configuration dump and reload has been fixed.