Neues vom PostgreSQL Planet
Cornelia Biacsics: Contributions for week 43
On 27 Oct, the Warsaw PostgreSQL User Group met.
Organizers:
- Alicja Kucharczyk
- Adam Wołk
- Tomasz Gintowt
Speaker:
- Tomasz Gintowt
On 30 October, PostgreSQL PG Down Under 2026 took place.
Organizers:
Ruohang Feng: Why I'm Maintaining a VectorChord Fork
Jimmy Angelakos: Postgres Edinburgh October 2026 Meetup Recap
Right after the Apache Software Foundation's Community Over Code in Glasgow, we found ourselves the following day in Edinburgh for our October meetup, where Elizabeth Christensen (Snowflake) went over what's new in Postgres 18 and 19.
Elizabeth Christensen walking us through the Postgres versions timeline
Dave Stokes: Is PostgreSQL Really Winning?
The November 2026 DB-Engines rankings are out. PostgreSQL is the only database in the top four whose line is going up and to the right.
Oracle, MySQL and Microsoft SQL Server all lost points this month, and all three are down from a year ago. PostgreSQL gained points on both counts. It now sits just 3.84 points behind SQL Server for third place. On the past year's trend, PostgreSQL could move ahead of SQL Server as early as next month.
Dimitri Fontaine: Postgres logical replication beyond one writer
In 2014, if you wanted Postgres servers on several continents, each of them accepting writes and all of them sharing their rows, there was one serious open source answer: BDR, from 2ndQuadrant. It needed a patched PostgreSQL 9.4 and a plugin, which means it needed a server that was not Postgres.
Jimmy Angelakos: Establishing the PostgreSQL Standard: PGConf.dev 2026 Part Two
Again, apologies for the delay. PGConf.dev was back in May, and it has taken me until November to follow up on Part One.
Stefanie Janine: PostgreSQL Conference Europe Wrapup
This years conference took place in Valencia, Spain, from Tuesday October 20 until Friday, October 23. We had a whole conference center for the conference, the Palacio de Congresos Valencia.
In previous years the first day was training, later community stuff. Now it is the last day for the community day events.
Mats Kindahl: Building a Table Access Method, Part 7: Storing and reading rows
Every memtable table now has an arena with a proper lifecycle, but nothing is stored in it. This post stores rows in the arena and reads them back with a full table scan. Along the way it shows what tuple format to use for efficiency, how any backend finds the arena of a table, how space is handed out inside the arena, and the format of TIDs and why they are needed. It also settles which rows a transaction is allowed to see, since two backends can now work on the same table at the same time.
Magnus Hagander: Nordic PGDay 2027 - Sponsorships for Nordic PGDay 2027 Are Now Open
We’re excited to announce that sponsorship opportunities for 2027 Nordic PGDay are now available. Our event returns to Stockholm, bringing together attendees from all over the Nordic region. Developers, DBAs, and users, meet for a day of learning and networking.This years main conference will be held in Stockholm, Sweden, and for the first time we will also run an auxiliary event in Gothenburg - and sponsorships cover both!
Sponsoring is a great way to connect with the PostgreSQL community, gain visibility, and show your support for our open source community.
Gabriele Bartolini: CloudNativePG reaches CNCF Incubation: another rung on the ladder
CloudNativePG is now a CNCF Incubating project, and it is a long way from the days when running PostgreSQL in Kubernetes was called an anti-pattern. This is a personal look at the road that led here: a cloud native initiative started at 2ndQuadrant in 2019, its quality-first mindset, the long-term support of EDB after the acquisition and the open sourcing of the project, a rejected Sandbox application in 2022 and the decision we took at KubeCon Atlanta.
Vibhor Kumar: Autonomous Postgres at PGConf.EU 2026: From Scripts to Self-Driving, and the Primitives in Between
On Friday, 23 October 2026, the last day of PGConf.EU in Valencia, almost 40 practitioners, builders, and skeptics gave up a community-day morning to ask one question: how real is “Autonomous Postgres” today?
Aleksei Aleinikov: Navicat 18 Review: Is It Worth It for PostgreSQL? Tested on 10M Rows
Most database client reviews are a tour of the feature list. I wanted to know something narrower: when you open Navicat 18 and put it in front of a real table, which of the new features do you actually find, and which of them hold up?
So I connected it to PostgreSQL with a table of 10 million rows and went through the headline features one by one. This is the list of what I saw: what worked on the first try, what was hidden, and one AI answer that needed a second look.
Note
Chris van Eijk: server closed the connection unexpectedly in PostgreSQL
Christophe Pettus: All Your GUCs in a Row: row_security
Vadim Yatsenko: Splitting the Read-Only Transaction: Replica Reads Inside an Open Transaction
Radim Marek: Getting rid of a 4 TB table in PostgreSQL
GitLab has a public story about deleting the wrong thing. In January 2017 an engineer who was trying to restore replication wiped a data directory they believed was on the secondary. It was on the primary. The postmortem they published afterwards is still one of the better things written about a database outage.
Igor Suhorukov: pg_vexec one month on: ahead of ClickHouse on Parquet, close behind on MergeTree
It’s been exactly one month since I published my work porting Greenplum to PostgreSQL 19 and isolating the minimal PostgreSQL core patches needed to run this minimal fork. It all started as a way to extract its ORCA analytical query planner and turn PostgreSQL into a modern, vectorized, high-performance DBMS. And I pulled it off! After a month of development, the database keeps getting faster. I’m now working on a GPU version.
Shaun Thomas: Burnt TOAST
A financial firm hired me in 2010 to revise their Postgres cluster architecture. During my stint there, I learned a healthy respect for their event_log table. But perhaps “respect” is the wrong word here, as it was more of a deep loathing. This table, you see, was the canonical ledger of system events and consisted of several million rows.The high row count wasn’t a problem by itself. We kept a tight visibility window and archived frequently. Unfortunately for us, one of the columns was an unconstrained TEXT type that commonly held a large blob of XML.
Robert Haas: Postgres 19 is late, and it's AI's fault
Over the past decade, the timing of PostgreSQL major releases has become very predictable: no earlier than the middle of September, and no later than the middle of October. This year is going to be different. PostgreSQL 19 most likely won’t be released until November, and it’s not impossible that the project could decide to postpone the release further.
Regina Obe: PostGIS 3.7.0
The PostGIS Team is pleased to release PostGIS 3.7.0! Best Served with PostgreSQL 19 RC 1 , GEOS 3.15.0 , postgis_tiger_geocoder 2025.2 , and address_standardizer.
