Postgres 19 GA set for Nov 19; SQL/PGQ graph queries cut to PG20
53 reverts forced an extra RC2 — many surfaced by AI code review — so PG18 stays the safe upgrade; and Taiwan weighs a criminal AI-chip export ban on China.
Copy markdown
Nov 19 GA, with a new RC2 slotted in first
The release team set PostgreSQL 19's GA for November 19 and added a previously unplanned RC2 on November 12 to get accumulated back-branch fixes in front of testers. RC1 still shipped October 15 on schedule. If you're planning migrations, pad your timeline and don't pin production to 19.0 until GA actually lands.
SQL/PGQ graph queries are out — wait for PG20
The marquee feature — property-graph queries over your existing tables — was pulled in a 47-commit, ~16,000-line revert and pushed to PostgreSQL 20. Also gone from 19: ALTER TABLE MERGE/SPLIT PARTITION, online data checksums, and the lz4-default TOAST compression change. If your roadmap assumed any of these in 19, it just slipped roughly a year.
AI code review is quietly reshaping the release
PostgreSQL has logged 53 reverts this cycle versus roughly 44 for PG18, and maintainers say most of the late ones trace to in-depth AI-generated reviews and reproducible test cases. Robert Haas even ran an AI-assisted 'scary bug contest' that flagged at-risk features like RI fast-path FK checks and postgres_fdw stats import. There's still no official AI-contribution policy — and PG18 is the recommended safe upgrade today.
Taiwan weighs a criminal ban on AI-chip exports to China
Taipei is reportedly considering making unauthorized shipments of advanced AI servers and chips to any Chinese buyer a criminal offense, aligning with US pressure during ongoing trade talks. If it passes, expect tighter supply and more scrutiny on the Nvidia hardware that ultimately sets your inference prices.