On Thursday, Feb 13th, the PostgreSQL Global Development Group (PGDG) released their regularly scheduled minor releases of PostgreSQL: 17.3, 16.7, 15.11, 14.16, and 13.19. These releases, among other bugfixes, resolved a CVE within PostgreSQL, so a sense of urgency in releasing them to our customers was bred. This, in turn, kicked off a flurry of activity within Crunchy as we readied Crunchy Postgres via Automation (CPA) for release to ship these new PostgreSQL releases. As we dove into the release process and began our internal testing, word came down from PGDG that the CVE fix was flawed and new PostgreSQL releases would be forthcoming.

Opting not to release known bad software, we continued our release testing efforts, but culled some of the tests that specifically involve the PostgreSQL releases (since we would have to do them again for the new releases). True to their word, on Thursday, Feb 20th, PGDG released PostgreSQL 17.4, 16.8, 15.12, 14.17, and 13.20 kicking off our internal release process once again. This time, we ran the full suite of release tests; and ran right into a corner case with our PostgreSQL minor version upgrade that prevented the upgrade from working. And thus, we had to scrap the CPA 2.2.2 and 2.1.7 releases, fix the upgrade issue, and start our release process over once again for CPA 2.2.3 and 2.1.8!

Thankfully, Jim is the man when it comes to managing back-branch releases and he and Yorvi got everything sorted, tested, and released on Fri, Feb 28th. Huge shout-out to both of these guys for managing the releases, doing the testing, and getting this into the hands of our customers!

But, the drama doesn’t stop there. On Friday, as we were releasing, we were informed of an upcoming CVE announcement on Tues, Mar 4th from the Go community. As a significant portion of our components are Go-based, this means that our Build team will be rebuilding the stack, and we’ll be doing the release dance again. Expect to see CPA 2.2.4 and 2.1.9 within the next fortnight. Maybe after these releases, I’ll send Jim on vacation or something. 😁

Crunchy Data customers can review the full release notes here to see all the changes in these CPA releases. And if you missed any of the prior entries in this series, you can see them all here. Happy upgrading, and we’ll talk again soon.

:wq