Neues vom PostgreSQL Planet
Munaf Khatri: Testing: Auto-generated Unit, Integration and Data leakage tests for PostgreSQL, Supabase and Neon
A PostgreSQL database holds logic as well as data, in functions, triggers and Row-Level Security (RLS) policies. On Supabase and Neon much of that logic can be reached straight from the browser. UnitAutogen for PostgreSQL generates three kinds of test for it, together with the mock data each test needs, so nothing is written by hand.
Radim Marek: B-tree pages, sorted and sparse
So far, the storage internals series has focused on heap pages. We began by opening the 8KB page, then traced MVCC visibility through xmin, xmax, and snapshots. Next we observed HOT updates evade index maintenance, and finally tracked VACUUM as it went through its phases.
Andreas Scherbaum: PostgreSQL Berlin November 2026 Meetup
On 4th of November, 2026, we had the PostgreSQL November Meetup in Berlin. AWS hosted it again, this time we had two speakers from Germany and UK.
The Meetup took place in the Amazontower (EDGE East Side Tower Berlin) in Berlin, across the Uber Arena and right next to the East Side Mall.
Mats Kindahl: Building a Table Access Method, Part 8: Cache invalidation
A backend keeps its mapping of the arena in its cache. As a result, if another backend drops or truncates the table, the memory of the old arena is not returned until that backend disconnects, so the cache has to be invalidated when the relation changes. This post uses the relcache invalidation messages of Postgres to find out when a table has changed, shows why the callback can only remember what has to be done, and detaches the mappings when the transaction ends.
Laurenz Albe: Don't dream it, be it!
No, this is not in commemoration of the late Tim Curry. After repeatedly writing about the Swiss PGDay, I want to share a personal impression from the European PostgreSQL conference 2026.
Ruohang Feng: PostgreSQL Ate the Database World. Now the Giants Are Eating Postgres Companies.
Mehmet Ince: Part 3/6 | How I Ended Up Turning a 22-Year-Old PostgreSQL Type-Confusion Primitive into RCE (CVE-2026-6460)
If you had told me in April 2026 one question “Mehmet, can we use managed PostgreSQL for this project?” would send me into the deepest rabbit hole of my life, I would have laughed.
Months later, I finally found the bottom of that rabbit hole. It was a 22-year-old zero-day in PostgreSQL core.
In this blog post you will read a story of how I ended up uncovering a new class of type-confusion vulnerabilities in PostgreSQL.
Hubert 'depesz' Lubaczewski: What LLMs do to PostgreSQL and DBAs
Alicja Kucharczyk: What your PostgreSQL needs before Black Friday
On Black Friday, many more people use your application at the same moment. For PostgreSQL that means more connections, more sessions that want the same rows, and more cleanup work and transaction log in the same hour. This article shows which limits a peak usually reaches first, which of them a bigger server does not remove, how to check each one on your own server with plain SQL, and which changes need a restart and therefore belong before your change freeze.
Cornelia Biacsics: Contributions for week 44
On 4 November, the PostgreSQL Meetup Group Berlin met.
Organized by:
- Andreas Scherbaum
- Daria Aleshkova
- Oleksii Kliukin
- Sergey Dudoladov
Speakers:
Richard Yen: An Index Scan Is Only Half the Story
Also posted in Microsoft Blog for PostgreSQL
Same Query, Same Index, Different PerformanceI recently worked with a customer planning a migration from on-premises PostgreSQL to Azure Database for PostgreSQL. During performance testing, they noticed something troubling: a query that completed in tens of milliseconds would now take 1-2 seconds in the Azure environment being evaluated.
Maki Majima: Two migrations collide: one loud failure, one silent one
In the previous post I argued that migrations don’t earn Git’s protections by being made of files: two incompatible schema changes live in two separate migration files, so there is nothing to textually conflict, and both branches merge clean. The repository accepts the pair without comment.
Chris van Eijk: json vs jsonb in PostgreSQL: size and speed, measured
Vadim Yatsenko: The Server-First Reader Pool: Exact Connection Reuse and Hot-Path Performance
Hollis Varden: Thirteen small measurements on PostgreSQL 18
These are thirteen things I measured in one sitting. Each one is small. A few of them surprised me anyway.
SetupPostgreSQL 18.6, built from source, default settings (work_mem 4MB, shared_buffers 128MB, 2 parallel workers per gather). MacBook Air M5, 10 cores, 24 GB RAM, internal SSD. This is a different machine from my earlier posts, so don't compare times across posts.
Dave Stokes: Is PostgreSQL Really Winning Part 2: The Evidence Beyond the Rankings
My last post leaned hard on the DB-Engines ranking, and I admitted that ranking measures popularity, not installed base or revenue. Several of you called me on that, politely and otherwise. Fair enough.
