Postgres 19 slipped because review got better after the code was written. Re-review your old work now.

PostgreSQL 19 now ships around November 19, late, because LLM-assisted review raised the quality bar after its features were written, and I read that as a scheduling lesson, not a scandal. In his October 9 post on Peter Eisentraut's blog, the PostgreSQL committer at EDB counts about 8 to 10 significant features reverted after beta began. Some had real architectural defects. Many were small edge cases that review now finds fast, and then you're staring at a list of like forty defect reports.

Each fix might be three lines. Each one still gets read, tested and merged, and that fixed cost ran out the clock. The Register's October 16 report adds that pulled features like SQL Property Graph Queries will likely land in PostgreSQL 20. Eisentraut is clear the code predates vibe coding.

For builders, the move is simple. Point today's reviewer at yesterday's code before the deadline. Start with the oldest modules. Budget triage time for the long tail it finds.

The same goes for rules you wrote last quarter, including the ones your agents follow. A better reader finds what an older one missed. Let it find them on your schedule.