Sammlung von Newsfeeds
Radim Marek: TOAST: Where PostgreSQL hides big values
In earlier posts in this series we established that every heap tuple lives inside a strict 8KB page. Everything else is built on top of that hard limit: MVCC, HOT updates, and indexes that point at (page, line_pointer). And yet this still works:
Andrei Lepikhov: On Polymorphic Associations in Postgres
OUTER JOIN is a typical plague of ORM-based PostgreSQL configurations: the planner is still relatively poor at optimising it. At the same time, ORM frameworks — and 1C as a prominent example — often generate outer joins from standard templates, which opens the door to targeted optimisations. In this article, I dig into one such template — polymorphic reference resolution: what the pattern is, where it comes from (Rails, Django, Hibernate, Salesforce — not just 1C), how widespread it is, and why its structural properties make it possible to significantly speed up execution.
Christophe Pettus: All Your GUCs in a Row: client_encoding
Paolo Melchiorre: Upgrade PostgreSQL from 17 to 18 on Ubuntu 26.04
Howto guide for upgrading PostgreSQL from version 17 to 18 on Ubuntu, after its upgrade from version 25.10 (Questing Quokka) to 26.04 (Resolute Raccoon).
Christophe Pettus: All Your GUCs in a Row: checkpoint_flush_after and checkpoint_warning
Christophe Pettus: pgvector 0.8.2 and the Trouble With Parallel HNSW
Umair Shahid: Long-running transactions, job queues, and the cascade that wreaks havoc
A scheduled PostgreSQL migration step held an open transaction snapshot for hours during the initial data copy. A job queue running at production write velocity began to slow down. Twelve hours later, the queue was seven million rows deep, the primary was pinned at 100 percent CPU across 24 cores, and customer support was fielding complaints about delayed transactions.
Staging had validated the migration plan. Every rehearsal was green. And yet here we were.
Shaun Thomas: Why Postgres Lacks Transparent Data Encryption
If you've ever compared database feature matrices, you may have noticed something a bit peculiar. Oracle has Transparent Data Encryption. SQL Server has it. MySQL has it. Even MariaDB has it. But Postgres, which we all consider the best database engine? Conspicuously absent.It’s not that nobody wants TDE. Compliance frameworks like PCI DSS and HIPAA practically demand encryption at rest. Cloud deployments make the “stolen disk” threat model more tangible than ever.
Christophe Pettus: All Your GUCs in a Row: checkpoint_timeout and checkpoint_completion_target
Cornelia Biacsics: Contributions for week 19, 2026
On 12 May, 2026 the San Francisco Bay Area PostgreSQL Meetup Group met virtually, organized by Katharine Saar, Stacey Haysler and Christophe Pettus. Alex Yarotsky spoke at the event.
The Swiss PGDay Program Committee met to finalize the schedule:
- Marion Baumgartner
- Tobias Bussmann
- Andreas Geppert
- Johannes Graën
- Stefan Keller
- Michelle Willen
Community Blog Post:
Christophe Pettus: Patch Today: CVE-2026-6473
Antony Pegg: From Managed PostgreSQL to Production RAG: Build Your Own Ellie in pgEdge Cloud
If you've used docs.pgedge.com recently, you've probably met Ellie. Ask her how to set up multi-master replication, or what port the MCP Server listens on, and she pulls the relevant documentation, assembles it into context, and gives you a grounded answer with source citations. She doesn't guess or hallucinate. She finds the actual docs and synthesizes an answer from them.Ellie is a RAG Server deployment.
semab tariq: How to Cut Over After a PostgreSQL Migration
One Database at a Time, or All at Once?
You have deployed your new cluster. Now comes the work of moving your data and cutting over to it. Reading that sentence, you might assume cutover is something you figure out at the end, after the migration is done. And in practice, that is the order in which things happen. But technically, it is your cutover strategy that decides how you migrate, not the other way around.

