Ardent Performance Computing
Planet
Postgres 18.7 Debian and Redhat Packagers Protect You
Just a short & quick follow-up to [yesterdays blog] before I run out the door. I hadn’t been paying attention, and yesterday’s postgres release had a few surprises for me. I’m catching up now. First: read [Devrim’s blog] and [Lukas’ 5-minutes-of-postgres] for the TLDR. Second: I had this in yesterday’s blog – “RPM packaging now … Continue reading
Postgres 18.7 minor breaks ABI compatibility again
Edit Fri Nov 13 at 8:32am Pacific Time: short & quick follow up [Postgres 18.7 Debian and Redhat Packagers Protect You] Edit 11:54am Pacific Time: just realized Devrim Gunduz published a blog this morning on the same topic. [His blog is better than mine and more thorough]… just start there :) Postgres API and ABI … Continue reading
Postgres recovery_prefetch Considered Harmful and Causing Outages
Another story of something I saw in the field which surprised me. Turns out recovery_prefetch can cause outages. Something which has been happening quietly in the background all the time, but we didn’t notice until we looked close enough to see it. After a lot of work I discovered this was partly a case where … Continue reading
Agents Gone Awry on Postgres SBOMs: Start Over
If you were wondering, it’s the SBOM thing that I mentioned the other day. [Misc Learnings: SBOMs, Provenance and Attestations] Postgres Extensions in containers with full inventory, provenance and attestation. I’ve been using plenty of AI Agents to put this together. This blog is a little scattered (apologies) but as they say, I didn’t have time … Continue reading
Misc Learnings: SBOMs, Provenance and Attestations
In the past couple weeks, I’ve learned more about renovate, SBOMs, provenance and attestations than I ever wanted to know. (But if I’m being honest, I do enjoy learning a bit more about it.) Backstory is that I decided to make CNPG-Extensions an actually serious project. The original name was “Not-CNPG” as a joke about … Continue reading
Why Postgres Breaks Kubernetes container_memory_working_set_bytes Metric
Kubernetes metric container_memory_working_set_bytes is used for evicting/killing pods with too much memory use, especially if memory request < limit (don’t do this with Postgres). The metric is calculated from cgroups v2 memory.stat as current-inactive_file [source]. You’d assume it’s a good metric for memory usage in kubernetes. But with Postgres, this metric is very inaccurate for … Continue reading
Postgres Checkpoint Followup and Collation Visualization and Codex Luna
My previous article talked about the checkpoint happiness hint: You probably should not change the checkpoint_timeout setting from its default of 5 minutes. Checkpoint Followup Questions A good follow-up question was raised: can an HA replica can save you from downtime if you want to set a large checkpoint_timeout? It’s true that Postgres allows promoting … Continue reading
Happiness Hint: Alarm on Checkpoint Time
Before starting, I want to put a few things at the top: You probably should not change the checkpoint_timeout setting from its default of 5 minutes. Users who read tuning advice on the internet (or get bad AI advice) about increasing this setting usually don’t understand the risk and significance of trading for RTO/availability. Let’s … Continue reading
PGConf.dev 2026 Trip Summary
I’m back home from Vancouver. What a great week – in every way. I’ll try to share a few highlights here. Updated Happiness Hints First and foremost: after many years, the Happiness Hints have received a major update! Before the conference, I updated the hints based on all the feedback I’ve collected over the past … Continue reading
Zero autovacuum_vacuum_cost_delay, Write Storms, and You
A few days ago, Shaun Thomas published an article over on the pgEdge blog called [Checkpoints, Write Storms, and You]. I left a few comments [on LinkedIn]. This article is a great technical read about an important and overlooked topic – and I always love seeing real test results to illustrate the details. I don’t … 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
Recent Comments