--- title: "Postgres 19 loses SQL/PGQ (and its release date)" publication: "Postgres Weekly" issue: 664 published_at: "2026-09-09" canonical_url: "https://postgresweekly.com/issues/664" --- Plus query tuning across 16 billion rows, a Kafka broker embedded in Postgres, and why query planning locks unused indexes. #​664 — September 9, 2026 [Web Version](https://postgresweekly.com/issues/664) Together with [![ParadeDB\](https://res.cloudinary.com/cpress/image/upload/c_fill,g_auto,e_trim,w_1280,h_164/e_make_transparent/co_white,e_outline:17/cdd8ciarsq6m8xam8oc3.png)](https://paradedb.com/cloud) Postgres Weekly [![\](https://res.cloudinary.com/cpress/image/upload/w_1280,e_sharpen:60,q_auto/eqdy9a7btdaispdwx0yl.jpg)](https://www.postgresql.org/message-id/CA%2BTgmob9NY6m0YNFTQ4nFH2d0iC9SQRruDYxfndGKKzh8OC80w%40mail.gmail.com) [The _Scary_ Postgres 19 Patch Contest](https://www.postgresql.org/message-id/CA%2BTgmob9NY6m0YNFTQ4nFH2d0iC9SQRruDYxfndGKKzh8OC80w%40mail.gmail.com) — It’s not even Halloween yet, but in this fascinating thread on the `pgsql-hackers` list Robert Haas set out with Claude to _“evaluate which v19 patches were the scariest”_. One of them, [SQL/PGQ property graphs](https://www.cybertec-postgresql.com/en/handling-graphs-with-sql-pgq-in-postgresql/), has since [been dropped](https://github.com/postgres/postgres/commit/2b9e1aff4d3d933ae8ee377fef22c2af9c7797e8) from v19, but five remain… Robert Haas et al. 💡 There's some [more background to SQL/PGQ's removal](https://www.postgresql.org/message-id/CAAKRu_bEtjWYWhYxSo0o_t3DaZYRQd5PkC0abA0g9Mp4%2BovH0w%40mail.gmail.com) in a separate thread on `pgsql-hackers` too. [![\](https://res.cloudinary.com/cpress/image/upload/c_limit,w_480,h_480,q_auto/copm/8a4895a1.png)](https://paradedb.com/cloud) [Coming Soon: ParadeDB Cloud](https://paradedb.com/cloud) — We're building a fully managed ParadeDB: one Postgres for your application data, full-text search, vector retrieval, and aggregations. [Our early access waitlist is open now](https://paradedb.com/cloud). ParadeDB sponsor **POSTGRES 19: A FOURTH BETA AND SOME HARD CHOICES:** Originally expected later this month, Postgres 19's release date is now [officially TBD](https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items#Important_Dates), with a fourth beta expected on September 24. But [the 'scary patch' thread](https://www.postgresql.org/message-id/CA%2BTgmob9NY6m0YNFTQ4nFH2d0iC9SQRruDYxfndGKKzh8OC80w%40mail.gmail.com) _(above)_ shows that what's going to be in it remains an open question: - [Tom Lane was _"quite afraid"_ of SQL/PGQ](https://www.postgresql.org/message-id/646368.1787697184%40sss.pgh.pa.us) two weeks before it was pulled, with fixes still under discussion that needed catalog changes: _"I'd be willing to bet dinner that if we ship it in v19 there will be post-release bug discoveries that are unfixable until v20."_ - [David Rowley argued](https://www.postgresql.org/message-id/CAApHDvqBudqUpjckbbePwyQnfmCrEOj50pPOXnCR5H5AetAY3Q%40mail.gmail.com) for setting _"the revert bar a bit lower this year"_, given a perceived reduction in developer time available. [Bruce Momjian noted](https://www.postgresql.org/message-id/ao7-qUPXkwete2Bv%40momjian.us) the volume of security/CVE fixes is having an impact here. - And [Joshua Drake suggested moving the release to spring 2027](https://www.postgresql.org/message-id/CAJvJg-TDxNL%2BHWm27N4h2_O8wZ%3D7YapGcdcbpPyYbpWgUuwS%3Dg%40mail.gmail.com), rather than removing features: _"I would rather have a late 19 than all these great features and hard work gutted."_ [How to Optimize When You Can’t Do Anything](https://hdombrovskaya.wordpress.com/2026/08/25/how-to-optimize-when-you-cant-do-anything/) — Hettie had a production query on a 750GB, 16 billion row table that suddenly ran slow. Creating the right index wasn’t an option (it’d take over a day) but a close look at the underlying data led to an ingenious fix. Henrietta Dombrovskaya **IN BRIEF:** - 🇺🇸 [The PostgreSQL@SCaLE CFP is open](https://gorthx.wordpress.com/2026/09/08/the-scale-24x-cfp-is-open-get-your-postgres-talks-in/) till November 1. The Postgres track runs April 1-2 at [SCaLE 24x](https://www.socallinuxexpo.org/scale/24x) in Pasadena. - 🇮🇳 [PGConf India 2027](https://www.postgresql.org/about/news/pgconf-india-2027-dates-announced-and-cfp-open-3370/) is back next March 2-5 in Bengaluru. [The CFP](https://pgconf.in/cfp) is open till October 15. - [Postgres's RPM repo now covers Amazon Linux 2023](https://people.planetpostgresql.org/devrim/index.php?/archives/128-PostgreSQL-RPM-repo-comes-to-Amazon-Linux-2023!.html). [Sixteen Locks Ought to Be Enough for Anybody](https://thebuild.com/blog/sixteen-locks-ought-to-be-enough-for-anybody/) — Did you know that, when planning a query, Postgres takes a (weak) lock on every index on the table whether it uses them or not? This is usually fine, but _until Postgres 18_ this could sting once a query touched more than 16 tables and indexes combined. Christophe Pettus 📄 [Inserting State Transitions in Postgres](https://thoughtbot.com/blog/inserting-state-transitions-in-postgres) – An append-only status table gives you full history, but two concurrent transitions can both insert. Here's how to prevent the conflicts. Thiago Araújo Silva (thoughtbot) 📄 [From the Trenches: My Path Through Postgres](https://www.pgedge.com/blog/from-the-trenches-my-path-through-postgres) – Twenty years of Postgres war stories, from a one-time MySQL advocate. Shaun Thomas 📄 [Fix Circular Role Dependencies Before Upgrading RDS and Aurora Postgres](https://aws.amazon.com/blogs/database/resolve-circular-role-dependencies-during-upgrades-of-amazon-rds-for-postgresql-and-amazon-aurora/) Ravi Teja Adabala (Amazon) 📄 [Postgres Calculations and the Ambiguity of `NULL`](https://www.crunchydata.com/blog/postgres-calculations-and-the-ambiguity-of-null) Christopher Winslett (Crunchy Data) 📰 Classifieds 🧊 Paying SSD prices for data nobody reads? [ColdFront tiers old Postgres rows to S3 automatically](https://github.com/pgEdge/coldfront), the open source way. --- 🎟️ Join us at [Supabase Select](https://supabase.link/JKX1Ifb) on October 2. Get first-hand information about what's coming soon in Supabase. [Apply to attend with 25% off: SUPAWEEKLY](https://supabase.link/JKX1Ifb). **RELEASES AND CODE:** [![\](https://res.cloudinary.com/cpress/image/upload/w_1280,e_sharpen:60,q_auto/varezths9zhsyun4zhhh.jpg)](https://rynr.dev/blog/kafgres/) [Kafgres: A Kafka-Compatible Broker Embedded Inside Postgres](https://rynr.dev/blog/kafgres/) — A [pgrx](https://github.com/pgcentralfoundation/pgrx)-powered extension that serves the Kafka wire protocol from a Postgres background worker, so standard Kafka clients can produce, consume, and rebalance consumer groups against topics stored in your database. Raynor Elgie [chdb: An Extension for Fast Imports from S3, GCS and Azure](https://clickhouse.com/blog/introducing-chdb-postgres) — ClickHouse’s chDB engine, wrapped as an extension for bulk imports and exports. `COPY` (or `CREATE TABLE`) can pull Parquet, Avro, ORC, Arrow and more from S3, GCS, Azure or over HTTP. Early days, but promising. David Wheeler (ClickHouse) - [pg_hardstorage 1.4](https://www.pghardstorage.org/) – Featured in [issue 654](https://postgresweekly.com/issues/654), Cybertec's streaming-first single Go binary backup/recovery tool has continued to mature, and 1.4 is a fix-heavy release, notably for its pgBackRest, Barman and WAL-G compatibility shims. - [Ivory 2.0](https://github.com/veegres/ivory/releases/tag/v2.0.0) – A web UI originally for operating HA Postgres clusters running under Patroni, but now with a plugin architecture for supporting systems like MongoDB and Redis too. - [Barman 3.20](https://github.com/EnterpriseDB/barman/releases/tag/release/3.20.0) – EDB's backup/recovery manager adds streaming multipart uploads to Google Cloud Storage, Zstd cloud backups, and faster compressed restores. - [pg_cron 1.6.8](https://github.com/citusdata/pg_cron/releases/tag/v1.6.8) – Adding Postgres 19 and native Windows build support. - 🌐 [PostGIS 3.7.0 RC2](https://postgis.net/2026/09/PostGIS-3.7.0rc2/) **Got a new email?** You can [change your address here](https://postgresweekly.com/edit_subscription/*|UID|*). --- **Bored of us?** [Click here to stop getting Postgres Weekly](https://postgresweekly.com/leave/*|UID|*). --- **Got a link for us?** Reply and tell us. We can't include everything but we'll look at anything you send. _Thanks!_ --- Published by Cooper Press Ltd. Fairfield Enterprise Centre, Louth, LN11 0LS, United Kingdom Postgres, PostgreSQL and the Slonik Logo are trademarks or registered trademarks of the PostgreSQL Community Association of Canada. [Stop getting this newsletter](https://postgresweekly.com/leave/*|UID|*).