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.

1.3.1

This release fixes a bug discovered on Mac OSX due to the usage of the builtin declare.

1.3.0

This release introduces the new switch command that allows a user to change the currently linked in PostgreSQL version, similar to use but without having the instance to be started.

Thanks to @thanodnl for the work on this new command.

v.1.2.2

This release fixes a problem with the configuration writing and loading in case of rebuilds of the same PostgreSQL version are issued.

Configuration management

The configuration files are now contained into a config subdirectory, so that it is easier to "move" or backup all the configuration files.
Moreover, the configuration files changed their name to (i) be not hidden and (ii) have a shorter name (e.g., 10.conf to refer to PostgreSQL 10.x configuration).
The special subocommand config migrate does the upgrade of your existing configuration from previous versions of pgenv.