PostgreSQL 19 drops SQL/PGQ graph queries over bugs, adds concurrent REPACK

PostgreSQL developers decided to pull SQL Property Graph Queries from version 19 after reviewing unresolved bugs that could surface after release. Tom Lane, a longtime contributor, warned that shipping the feature now would likely lead to unfixable defects until the next major version. The project cited community feedback favoring more testing before a general availability release. A fourth beta of PostgreSQL 19 is scheduled for September 24, giving testers more time to evaluate other changes.

Database administrators have long faced downtime when running VACUUM FULL, which holds an exclusive table lock and blocks reads and writes. The new REPACK command introduces a CONCURRENTLY option that allows most of the operation to proceed while other transactions access the table. Although a brief exclusive lock is still required to swap the rewritten table and index files, the lock duration is much shorter than with VACUUM FULL. This reduces the likelihood of middle-of-night calls caused by maintenance tasks.

For developers, the absence of SQL/PGQ means applications that depend on standardized graph query syntax must either implement workarounds or wait for a later PostgreSQL release. The concurrent REPACK feature helps operators reclaim disk space with less interruption, but it does not eliminate the need for an exclusive lock entirely. Consequently, teams must adjust their maintenance windows and query strategies based on what is available in v19.