Ardent Performance Computing
Search
Jeremy
Building and running reliable data platforms that scale and perform.about.me/jeremy_schneiderTesting CloudNativePG Preferred Data Durability
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→
Data Safety on a Budget
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→
Postgres Replication Links
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→
Losing Data is Harder Than I Expected
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→
Run Jepsen against CloudNativePG to see sync replication prevent data loss
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→
Graviton2 versus Graviton4
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 versus Debian
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→
Waiting for Postgres 18 – Docker Containers 34% Smaller
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→
Testing loadBalancerSourceRanges with CloudNativePG on Azure Kubernetes
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→
Postgres Per-Connection Statistics
I’ve had a wish list for a few years now of observability-related things I’d love to see someday in community/open-source Postgres. A few items from my wish list: As I’ve noted in a few places, there has been slow and steady progress in Postgres over recent years. There’s also plenty of good discussion continuing on …Continue reading→
Disclaimer
This is my personal website. The views expressed here are mine alone and may not reflect the views of my employer.I am currently looking for consulting and/or contracting work in the USA around the oracle database ecosystem.
contact:312-725-9249 orschneider @ ardentperf.com
Enter your email address to receive notifications of new posts by email.
Recent Posts
- Testing CloudNativePG Preferred Data DurabilityOctober 5, 2025
- Data Safety on a BudgetOctober 4, 2025
- Postgres Replication LinksOctober 2, 2025
- Losing Data is Harder Than I ExpectedSeptember 28, 2025
- Run Jepsen against CloudNativePG to see sync replication prevent data lossSeptember 1, 2025
Recent Comments
- Losing Data with PostgreSQL and Jepsen – Curated SQL onLosing Data is Harder Than I Expected
- Luiz Verona onRun Jepsen against CloudNativePG to see sync replication prevent data loss
- Jeremy onGraviton2 versus Graviton4
- Elevarq onGraviton2 versus Graviton4
- Best of Tech #74 - Atol Open Blog onUUID Benchmark War
Ardent Performance Computing