PostgreSQL 19's new REPACK CONCURRENTLY command reduces table lock time significantly
PostgreSQL 19 introduces a new REPACK command with a CONCURRENTLY option designed to reclaim storage space without prolonged table locking. The new feature aims to replace the functionality of VACUUM FULL or the pg_repack extension while allowing other operations to continue. Testing on PostgreSQL 19 beta 4 showed REPACK CONCURRENTLY reduced client blocking time from over 4 seconds to under one second during table reorganization. The improvement occurs because REPACK CONCURRENTLY only briefly locks the table at the end of the operation rather than throughout the entire process.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in