Share this post:
Upgrading IBM Cloud Compose for PostgreSQL
If you haven’t upgraded your Compose for PostgreSQL deployment to the latest security-fixed version, we’ll be upgrading it for you in the coming weeks. Read on for how you can still take control of the upgrade.
A month ago, we made new versions of Compose for PostgreSQL available on IBM Cloud so that users could upgrade on their own schedule to the latest releases which resolved two security issues.
Now that a month has passed, we are moving onto the next phase of the process where we upgrade our customers’ databases for them. It’s important, for the Cloud’s version of herd immunity, to have the latest versions of databases in place, which is why we are taking this step. The timer begins today.
Your own timetable
You will still be able to do an upgrade yourself on your own timetable over this month. If you’ve been looking to move up a Compose for PostgreSQL major version, now could be a great time to do it. If not, you can do a simple in-place upgrade. It is important to remember that the in-place, minor version upgrades of the database have no application-level breaking changes.
Thirty days from now, on October 15th, we’ll be implementing forced upgrades of existing PostgreSQL’s up to the highest minor version for their major version. That means 9.4.x PostgreSQL will be upgraded to 9.4.19, 9.5.x to 9.5.14 and 9.6.x to 9.6.10.
We expect the upgrade work to be completed by mid-November.
There are added benefits to this upgrade for users too. We’ll be ensuring that all upgraded PostgreSQL deployments will be using Patroni as a core component of their high availability management. Patroni developed from a Compose project and replaced that project on Compose for PostgreSQL. If you have an older deployment, you’ll also find that you benefit from better more verbose logging.
Again, it’s not too late to take control of your own upgrade. Simply go to the Settings tab and select an in-place version upgrade for your database.
We are also be moving the new PostgreSQL versions – 9.4.19, 9.5.14 and 9.6.10 – to preferred status, as previously announced. This will ensure that all new deployments will be using the latest version.
These changes will bring a better PostgreSQL to all Compose users.