v38

PostgreSQL version upgrade

This release upgrades PostgreSQL to version 11.4.

For more information about the upgrade, in particular about tested upgrade paths, refer to the Upgrading section of the README.

v37

PostgreSQL version upgrade

This release upgrades PostgreSQL to version 11.3.

For more information about the upgrade, in particular about tested upgrade paths, refer to the Upgrading section of the README.

v36

This release upgrades PostgreSQL to version 11.2.

For more information about the upgrade, in particular about tested upgrade paths, refer to the Upgrading section of the README.

v35

Avoid failure of bbr restore when restoring a table not present anymore (thanks @rkoster!)

v34

Changes:

• Fix a bug in the bbr-postgres-job when not using bosh links (#48, thanks @rkoster!)

v33

Changes:

• Allow specifying port and databases for bbr-postgres-job when not using bosh links (#46)

v32

PostgreSQL version upgrade

This release upgrades PostgreSQL to version 11.1.

For more information about the upgrade, in particular about tested upgrade paths, refer to the Upgrading section of the README.

If your databases use hash indexes, you must rebuild them after pg_upgrade by running /var/vcap/store/postgres/pg_upgrade_tmp/reindex_hash.sql after the bosh deploy.

v31

The backup and restore functionality now optionally supports:

• backup and restore from a separate instance group
• tls connections
• authentication using client certificates

v30

PostgreSQL version upgrade

This release upgrades PostgreSQL to version 9.6.10.

For more information about the upgrade, in particular about tested upgrade paths, refer to the Upgrading section of the README.

v29

New features:

• You can enable backup and restore through Bosh Backup and Restore. See documentation for details and current limitations.

Changes:

• Removed property databases.databases[n].run_on_every_startup deprecated since v20
• Fixed issue in stopping pg_janitor child processes
• Improved control jobs serviceability. Note that by default debug traces for control jobs are no longer printed; set the databases.enable_trace property to true to enable them.