Neues vom PostgreSQL Planet

Neues vom PostgreSQL Planet Feed abonnieren
Planet PostgreSQL
Aktualisiert: vor 31 Minuten 15 Sekunden

Jimmy Angelakos: Establishing the PostgreSQL Standard: PGConf.dev 2026 Part Two

3. November 2026 - 12:30

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

3. November 2026 - 0:00
PostgreSQL Conference Europe 2026

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

2. November 2026 - 20:54

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

2. November 2026 - 16:28

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

2. November 2026 - 14:36

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

2. November 2026 - 11:48
A morning in Valencia

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

2. November 2026 - 7:30

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

2. November 2026 - 1:00
PostgreSQL's server closed the connection unexpectedly, measured in six clients: what the server log says per cause, where the reason goes, and lost COMMITs.

Christophe Pettus: All Your GUCs in a Row: row_security

1. November 2026 - 15:00
`row_security = off` doesn't disable row-level security—it triggers an error when a policy would apply. (I consult on PostgreSQL through PGX Inc..)

Vadim Yatsenko: Splitting the Read-Only Transaction: Replica Reads Inside an Open Transaction

1. November 2026 - 9:37
Read/write splitting is easy for single, autocommit statements. It gets hard the moment a client opens a transaction. Most proxies give up and send every statement inside a transaction to the primary, even the reads. This article is about a middle path we built into Polar Proxy: keep the transaction on the primary, but let its read statements borrow a replica connection.

Radim Marek: Getting rid of a 4 TB table in PostgreSQL

31. Oktober 2026 - 23:00

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

30. Oktober 2026 - 17:07

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

30. Oktober 2026 - 17:04

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

30. Oktober 2026 - 16:53

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

30. Oktober 2026 - 1:00

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.

Munaf Khatri: Supabase is one part of your HIPAA compliance

29. Oktober 2026 - 13:00

If you store PHI on Supabase, you need a signed BAA and a project set to High Compliance. That takes care of the platform. It doesn't cover your RLS policies, your functions or your audit tables, and a HIPAA review will ask about those too.

Supabase's shared responsibility model says the same. It tells you to "always apply Row Level Security (RLS)" and leaves the access rules on sensitive tables to you.

Christophe Pettus: All Your GUCs in a Row: restrict_nonsystem_relation_kind

29. Oktober 2026 - 2:00
PostgreSQL 16.4, 15.8, 14.13, 13.16 and 12.20 added a security parameter that only pg_dump uses. (I consult on PostgreSQL through PGX Inc..)

Igor Suhorukov: Which language should an AI agent use to search its memory: SQL or SPARQL?

28. Oktober 2026 - 10:24

Agent memory has been in fashion ever since agents appeared: it fights hallucinations and lets an LLM base its answers and decisions on your own information. Whether it is better to query that information from tables or from a graph is often decided on faith, after reading posts on the internet, without experiments and measurements of your own.

Nikolay Samokhvalov: Dump/restore done. Now what?

28. Oktober 2026 - 5:30
After pg_dump and pg_restore, by default the planner statistics and the visibility map are missing. One query: 32.6 s before VACUUM ANALYZE, 23 ms after.

Christophe Pettus: All Your GUCs in a Row: restore_command

28. Oktober 2026 - 2:00
PostgreSQL's `restore_command` asks for WAL segments one at a time until the command fails—and that failure marks the archive's end, whether it's real or not. (I consult on PostgreSQL through PGX Inc..)

Seiten