AlphaGazette
Menu

Tech

PostgreSQL 19 adds concurrent REPACK and standby WAIT FOR LSN

The PostgreSQL Global Development Group also shipped the pg_plan_advice extension and further speed work. The major version missed the usual September window after a pile of AI-related bug and security reports.

1 min read AI-generated

The PostgreSQL Global Development Group has released PostgreSQL 19. The server can reorganize a table through REPACK with a CONCURRENTLY option while other activity keeps running, and it adds the pg_plan_advice extension so operators can hold execution plans steadier and adjust query speed, along with more performance work.

Applications that read from standby servers can keep a consistent view of their own writes. A session on a standby uses WAIT FOR LSN to pause until write-ahead log replay reaches a log sequence number taken from the primary, then runs its query against data just written there. The timeout may be left out. When one is set and that replica is still behind, the command returns an error. Simon Willison gave an example that stores an LSN such as 0/0306EE20 and later waits with a timeout of 0.1s. He noted the same pattern in MediaWiki, which records the primary binlog position and, before reading, waits on MySQL with WAIT_FOR_EXECUTED_GTID_SET, falling back to MASTER_POS_WAIT.

New major versions usually appear in September. This one ran weeks behind schedule because the developers were swamped by AI- and LLM-driven bug reports and security issues, Phoronix reported. Simon Willison put the slip at two months and tied it mainly to that wave of AI-reported vulnerabilities. Several features once planned for this version were removed in September. The release notes carry the full list of changes.