Neues vom PostgreSQL Planet

Sooner or later, someone on the team reads about write skew. It is an unsettling read: two transactions, each correct on its own, each looking at data the other is about to change, both committing, and the database ending up in a state that no ordering of the two could have produced. READ COMMITT… (I consult on PostgreSQL through PGX Inc..)

For most of the last decade, every copy of pgAdmin that anyone has ever downloaded was built by a Jenkins server, and for most of that time it did the job perfectly well. It built the Debian and Red Hat packages, the Windows installer, the macOS app bundle, the Python wheel, the container image, the Helm chart and the documentation; it signed them, published them to the download site, and told me when something had gone wrong.

2026년 11월 17~18일 홍콩에서 열리는 PGConf.Asia 2026에서 EDB 전문가들이 PostgreSQL의 주요 기술과 운영 과제를 소개합니다. AI 기반 SQL 생성과 검색·RAG부터 스케일아웃 아키텍처, 성능 튜닝, CloudNativePG 및 TPA 기반 클러스터 관리까지 주요 발표 세션을 미리 살펴보세요.

`primary_conninfo` tells a standby where to stream WAL from—but only after the archive and pg_wal run dry. (I consult on PostgreSQL through PGX Inc..)

I packaged bigquery_fdw over 6 years ago. However if you tried to use bigquery_fdw from the PostgreSQL YUM or zypper repositories recently, there is a good chance it did not work: the Python modules it needs could not be imported by the interpreter it runs in. The packages that are in the repositories as of today fix that on RHEL 8, 9 and 10, Fedora 43, 44 and 45, Amazon Linux 2023, and SLES 15 and 16.

Debugging PostgreSQL connections requires stopping a backend before it does anything interesting. (I consult on PostgreSQL through PGX Inc..)

We’re wrapping up our series of articles reviewing the changes in PostgreSQL 19. The previous articles covered the first four CommitFests: 2025-07, 2025-09, 2025-11, 2026-01.

Somewhere in the multiverse, there is a version of you who attends every interesting talk at PGConf.EU.

Unfortunately, in this universe, PostgreSQL has parallel query execution. Humans don’t.

Last year, I created an Underground Map for Database Nerds to navigate PGConf.EU without getting lost in the schedule.

This is part 3 of a series about Postgres logical replication use-cases, and about how the feature set has evolved over the past ten years and ten releases (Postgres 10 through the Postgres 19 beta), one architecture at a time. Part 1 built a hub-and-workers system for write scalability and has the table of what each release added, which this post assumes.

How ctid-aware segment partitioning, an inverted DocId map, and bitmap postings accelerated ParadeDB's Wikipedia COUNT queries—then a look at the rest of search, where ParadeDB delivered 10–22x TIN's throughput on filtered and time-sorted Hacker News queries.