Are you in the Pacific Northwest? Since January 2024 we’ve been recording the presentations at Seattle Postgres User Group. After some light editing and an opportunity for the speaker to take a final pass, we post them to YouTube. I’m perpetually behind (I do the editing myself) so you won’t find the videos from this … Continue reading
This is the third post about running Jepsen against CloudNativePG. Earlier posts: First: shout out to whoever first came up with Oracle Data Guard Protection Modes. Designing it to be explained as a choice between performance, availability and protection was a great idea. Yesterday’s blog post described how the core of all data safety is copies of … Continue reading
Many experienced DBAs joke that you can boil down the entire job to a single rule of thumb: Don’t lose your data. It’s simple, memorable, and absolutely true – albeit a little oversimplified. Mark Porter’s Cultural Hint “The Onion of our Requirements” conveys the same idea with a lot more accuracy: We need to always make sure we … Continue reading
Our platform team has a regular meeting where we often use ops issues as a springboard to dig into Postgres internals. Great meeting today – we ended up talking about the internal architecture of Postgres replication. Sharing a few high-quality links from our discussion: Alexander Kukushkin’s conference talk earlier this year, which includes a great … Continue reading
This is a follow‑up to the last article: Run Jepsen against CloudNativePG to see sync replication prevent data loss. In that post, we set up a Jepsen lab to make data loss visible when synchronous replication was disabled — and to show that enabling synchronous replication prevents it under crash‑induced failovers. Since then, I’ve been … Continue reading
Are you in the Pacific Northwest? Want to learn more about topics related to this blog? At 3:15p on Thu Nov 13 in KubeCon Atlanta, I’ll be speaking with Leonardo Cecchi about distributed systems theory applied to standard open source postgres cluster reconfigurations. Jepsen is a testing framework for distributed systems that verifies safety guarantees … Continue reading
Just a short post, because I thought this was pretty remarkable. Below, I have screenshots showing the CPU utilization of two AWS instances in us-west-2 which are running an identical workload. They are running the CloudNativePG playground, which is a production-like learning and testing environment (all running virtually inside the single ec2 instance, which can … Continue reading
Collation torture test results are finally finished and uploaded for Debian. https://github.com/ardentperf/glibc-unicode-sorting The test did not pick up any changes in en_US sort order for either Bullseye or Bookworm 🎉️ Buster has glibc 2.28 so it shows lots of changes – as expected. The postgres wiki had claimed that Jessie(8) to Stretch(9) upgrades were safe. … Continue reading
On February 25, 2025 Christoph Berg committed the patch: This closed Debian bug 927182 which had been opened in April 2019 by Laurence Parry. That bug had raised concerns over the significant size increase of adding LLVM as a requirement to support Postgres JIT functionality. Postgres supports packaging LLVM as a separate optional package without … Continue reading
This option didn’t seem super widely documented from my initial searches online; it should be able to basically enforce layer 4 ingress/firewall rules at the individual service level. This is a quick test to check if it works. Steps were generated with ChatGPT, and mostly worked. It missed Azure provider registration, but I figure that … Continue reading
Recent Comments