Welcome to our third installment in this blog series discussing Crunchy Postgres via Automation(CPA). This week, we’re going to talk about the team that I work with, it’s membership, its structure, the responsibilities, etc.
read moreAs discussed last week, I’m back today to highlight the major differences between the 1.x and 2.x lines of Crunchy Postgres via Automation(CPA).
read moreIn March of ‘23, I took over as the Lead Architect of my employer’s Ansible-based automation for creating highly-available PostgreSQL clusters.1 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 moreSomeone at work thought it would be a good idea to give me access to the corporate blog so that I might post PostgreSQL-related things there and have them syndicated to Planet PostgreSQL. So my PostgreSQL ramblings will show up there now instead of here. This should be fun!
read more
I recently got a new Macbook Pro from work as my old one was having keyboard issues and since it was 3+ yrs old they deemed it not worth fixing. As you probably know, I spent a lot of time and effort on the previous mbp to get Gentoo up and running on it. I chose not to do so with this one.
read more