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.
read more
As previously mentioned in this Crunchy Postgres via Automation series, we now use a Bill of Materials (BoM) to ship tested-together versions of the components that comprise the CPA product. Accordingly, when the PostgreSQL Global Development Group (PGDG) releases new versions of PostgreSQL as they did yesterday, we have to iterate our BoMs to include these releases.
read more
Continuing our series on Crunchy Postgres via Automation, we’re here this week to discuss the highlights of our latest release line, v2.2. If you haven’t already, you can catch up on the differences between v1 and v2 and then come back, we’ll wait for you.
read more
In March of ‘23, I took over as the Lead Architect of my employer’s Ansible-based automation for creating
highly-available PostgreSQL clusters. Since then, I’ve been responsible for advancing the product: refactoring
the code, adding functionality, rethinking some of its core attributes, etc. I’ve also taken some steps to informally restructure the team that works on things to better divide up responsibilities and make everyone
more productive.
read more
We’ve had a small flurry of customers asking about tuning their OS for the best PostgreSQL performance. While the answer to this question is always ’that depends on your hardware and workload’ and involves a lot of iteration between changing a setting and benchmarking, I thought I’d take a moment to point out that once you do manage to dial-in the settings, you should be writing a profile and deploying to your systems for tuned to make use of. Please, for the love of $diety, stop editing sysctl.conf and friends!
read more