Crunchy PostgreSQL for PCF Release Notes

This topic provides release notes for Crunchy PostgreSQL for Pivotal Cloud Foundry (PCF) Tile.

v03.090511.108

Release Date: February 15, 2018

Software features in this release:

  • PostgreSQL minor release: 9.5.11
  • Component update: pgBackrest (1.25 to 1.28)
  • Component update: node_exporter (0.15.1 to 0.15.2)
  • Support for customizing bloat check schedule
  • Bugfix: Health check error may cause unnecessary failovers
  • Bugfix: Prometheus series errors from fast failover

    INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

    To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

    To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

    If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090510.107

Release Date: January 25, 2018

Software features in this release:

  • PostgreSQL minor release: 9.5.10
  • Added ‘Monitoring’ feature: using Grafana and Prometheus
  • Support for PostgreSQL Foreign Data Wrapper
  • Support for Redis Foreign Data Wrapper
  • Support for optionally enabling PL/R extensions
  • Support for additional PostgreSQL configuration options

    INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

    To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

    To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

    If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090510.106

Release Date: November 9, 2017

Software features in this release:

  • PostgreSQL minor release: 9.5.10
  • Component upgrade: PG common 184 to 187
  • Component upgrade: Backrest 1.20 to 1.25
  • Component upgrade: pgaudit_analyze 1.0.6 to 1.0.7
  • Fixed bug with SSH known hosts causing backrest failures
  • Fixed bug where replicas reported failing to BOSH
  • Tuned failover code to fence failed primaries

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090509.105

Release Date: September 15, 2017

Software features in this release:

  • Upgrade ODB SDK from 0.14.1 -> 0.17.0
  • Added service quotas for plans
  • Added configurable replica counts

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090509.104

Release Date: August 31, 2017

New tags included in this release:

  • PostgreSQL 9.5.9

Software fixes in this release:

  • Fixed bug where monit triggered PostgreSQL to restart
  • Fixed bug where failover didn’t repair fenced servers

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090508.103

Release Date: August 16, 2017

Security fixes included in this release:

  • Update stemcell to patch Ubuntu Linux kernel security vulnerability (USN-3385-2)

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090508.102

Release Date: August 14, 2017

Security fixes included in this release:

  • Security Vulnerability CVE-2017-7546: Empty password accepted in some authentication methods
  • Security Vulnerability CVE-2017-7547: The “pg_user_mappings” catalog view discloses passwords to users lacking server privileges
  • Security Vulnerability CVE-2017-7548: lo_put() function ignores ACLs

New tags included in this release:

  • PostgreSQL 9.5.8
  • PostGIS 2.3.3
  • PgAudit 1.0.6
  • pgBackrest 1.20
  • PLR 8.3.0.17

Software fixes in this release:

  • Fixed slow deprovision bug
  • Added primary to replica pool as a fallback for read queries
  • Added hourly job to repair fenced services
  • Fixed bug where HAProxy would not disconnect users after failover
  • Lifted replica limitation
  • Improved healthchecks for PostgreSQL

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090507.101

Release Date: July 14, 2017

Security fixes included in this release:

  • Prevent the tile from logging manifests generated by the broker when deploying PostgreSQL, because they contain sensitive information.

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v03.090507.100

Release Date: July 1, 2017

WARNING: This is the GA release, and is not compatible with the previous releases, including the beta release. Please see detailed release notes below for more information.

Features included in this release (for details on features please read the feature-overview document):

  • High-availability model
  • Auto-failover
  • On-Demand single-tenant service

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v02.090507.101

Release Date: May 23, 2017

WARNING: This is an updated beta release of the on-demand single-tenant service. This beta release is intended for evaluation purposes only. The final release of this software will include some changes that will likely break compatibility between this release and the next release.

Features included in this release (for details on features please read the feature-overview document):

  • On-Demand single-tenant service

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v02.090507.100

Release Date: May 12, 2017

WARNING: This is a beta release of the on-demand single-tenant service. This beta release is intended for evaluation purposes only. The final release of this software will include some changes that will likely break compatibility between this release and the next release.

Features included in this release:

  • On-Demand single-tenant service

INote: Crunchy PostgreSQL for PCF v3 relies on functionality released in PCF v1.9 – v1.12 to provide support for “on-demand broker” capability.

To implement this functionality, Crunchy Data has made material modifications to the Crunchy PostgreSQL for PCF manifest and does not currently provide a direct upgrade path from Crunchy PostgreSQL for PCF v1 or v2 to Crunchy PostgreSQL for PCF v3.

To avoid confusion between the two implementations, Crunchy Data has removed the Crunchy PostgreSQL for PCF v1 and v2 software versions from Pivotal Network. If you previously downloaded and deployed an evaluation copy of Crunchy PostgreSQL for PCF v1 or v2, Crunchy Data is happy to provide ongoing commercial subscription support.

If you are interested in commercial subscription support for Crunchy PostgreSQL for PCF, please contact sales@crunchydata.com.

v1.0.8

Release Date: March 10, 2017

Features included in this release:

  • Crunchy PostgreSQL v9.5 and PostGIS v2.3
  • Leader/follower PostgreSQL architecture
  • Load-balanced read replicas
  • Load-balanced brokers
  • Automated backups with pgBackrest
  • Self-managed databases

v1.0.6

Release Date: January 13, 2017

Features included in this release:

  • Crunchy PostgreSQL v9.5 and PostGIS v2.2
  • Leader/follower PostgreSQL architecture
  • Load-balanced read replicas
  • Load-balanced brokers
  • Automated backups with pgBackrest
  • Self-managed databases
Create a pull request or raise an issue on the source for this page in GitHub