Neues vom PostgreSQL Planet
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.
Christophe Pettus: All Your GUCs in a Row: scram_iterations
Chris Travers: PostgreSQL, NUMA, and the Cloud
Ruohang Feng: PostgreSQL Ecosystem Update: The AI Bug-Hunting Crunch
Ahsan Hadi: Zero Downtime In-Place Major PostgreSQL Upgrades on a Distributed PostgreSQL Cluster
In my last post I walked through a rolling major version upgrade: add a brand new node on the new version, let it join the Spock cluster, retire the old node. It works well, but it assumes you can stand up an extra server for every node you need to upgrade. A lot of customers I talk to cannot. Either the hardware is not there, or the database is too big to hold a second full copy.For them there is a second option. Upgrade each node in place with .
SHRIDHAR KHANAL: PostgreSQL Minor Version Upgrade on RHEL 9: A Step-by-Step Guide with Rollback
- A minor upgrade, such as 15.13 to 15.19, only replaces the binaries. The data directory stays as it is, so there is no pg_upgrade, dump and restore, or new cluster.
- The upgrade command takes seconds.
Nikolay Samokhvalov: UUIDv4 vs UUIDv7: what a random primary key costs in Postgres
Ruohang Feng: Taking Over Another PostgreSQL Extension: vchord Yesterday, pg_mooncake Today
Bruce Momjian: New Presentation
I just gave a new presentation at FOSS4G North America titled Can AI Write SQL? The talk is a follow-up to my Building an Mcp Server Using Postgres talk, and explores how well AI can write SQL queries, and how to help AI be more effective.
Ilya Kosmodemiansky: The “default” postgresql.conf
pg_settings, reload versus restart, max_connections, reserved connections and TCP keepalives
