Ardent Performance Computing
Linux
The Scott Shambaugh Situation Clarifies How Dumb We Are Acting
My personal blog here is dedicated to tech geek material, mostly about databases like postgres. I don’t get political, but at the moment I’m so irritated that I’m making the extraordinary exception to veer into the territory of flame-war opinionating… This relates to Postgres because Scott is a volunteer maintainer on an open source project … Continue reading
Postgres client_connection_check_interval
Saw this post on LinkedIn yesterday: I also somehow missed this setting for years. And it’s crazy timing, because it’s right after I published a blog about seeing the exact problem this solves. In my blog post I mentioned “unexpected behaviors (bugs?) in… Postgres itself.” Turns out Postgres already has the fix; it’s just disabled … Continue reading
How Blocking-Lock Brownouts Can Escalate from Row-Level to Complete System Outages
This article is a shortened version. For the full writeup, go to https://github.com/ardentperf/pg-idle-test/tree/main/conn_exhaustion This test suite demonstrates a failure mode when application bugs which poison connection pools collide with PgBouncers that are missing peer config and positioned behind a load balancer. PgBouncer’s peering feature (added with v1.19 in 2023) should be configured if multiple PgBouncers are being used … Continue reading
KubeCon 2025: Bookmarks on Memory and Postgres
Just got home from KubeCon. One of my big goals for the trip was to make some progress in a few areas of postgres and kubernetes – primarily around allowing more flexible use of the linux page cache and avoiding OOM kills with less hardware overprovisioning. When I look at Postgres on Kubernetes, I think … 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
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
Challenges of Postgres Containers
Many enterprise workloads are being migrated from commercial databases like Oracle and SQL Server to Postgres, which brings anxiety and challenges for mature operational teams. Learning a new database like Postgres sounds intimidating. In practice, most of the concepts directly transfer from databases like SQL Server and Oracle. Transactions, SQL syntax, explain plans, connection management, … Continue reading
Kubernetes Requests and Limits for Postgres
As Joe Drumgoole said a few days ago: so many Postgres providers. Aiven, AWS, Azure, Crunchy, DigitalOcean, EDB, GCP, Heroku, Neon, Nile, Oracle, Supabase, Tembo, Timescale, Xata, Yugabyte… 🤯 I’m sure there’s more I missed. And that’s not even the providers using Postgres underneath services they offer with a different focus than Postgres compatibility. (I … Continue reading
Copy-and-Paste A New Postgres Dev Env In 5 Min
You can cut-and-paste the following commands to quickly get a new & clean dev environment for working with PostgreSQL source code. This includes Michael Paquier’s powerful script kit for managing the PostgreSQL development environment. Setting up from scratch takes me about 5 minutes, plus 3 minutes to configure, compile and install PostgreSQL for testing. Running the … Continue reading
Disclaimer
This is my personal website. The views expressed here are mine alone and may not reflect the views of my employer.
contact: schneider @ ardentperf.com
Ardent Performance Computing 
Recent Comments