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