PostgreSQL gains CONCURRENTLY option for REPACK in recent commit

It has been reported that a commit to the PostgreSQL repository adds a CONCURRENTLY option to the REPACK command (commit 28d534e2ae0ac888b5460f977a10cd9bb017ef98). The change showed up on GitHub and was picked up in community discussion on Lobsters. Small tweak? Hardly. This is the kind of hygiene upgrade DBAs notice immediately.

What changed

Allegedly, the commit introduces support for a CONCURRENTLY qualifier on REPACK, mirroring the familiar pattern used by commands like REINDEX CONCURRENTLY. The patch modifies the command handling so that repacking operations can be requested in a concurrent mode, rather than forcing the same level of exclusive locking that a blocking repack would require. The commit hash above is the source; consult the repository to inspect the exact diffs.

Why it matters

For anyone who’s ever scheduled maintenance windows around index or table repacks, this is welcome news. Running heavy maintenance without long locks means fewer outages and less hair-pulling at 3 a.m. It’s part of a broader trend in the database world: make maintenance online, safe, and less disruptive. Will it be a panacea? No. But for busy production clusters it could shave precious downtime off routine tasks.

Status and next steps

It has been reported that the change is in the upstream GitHub history now; documentation and broader testing will determine how quickly it lands in stable releases and distributions. If you manage PostgreSQL in production, try it out in a staging environment and follow the repo discussion for caveats and performance notes. After all, the proof is in the metrics — and in a DBA’s relieved sigh.

Sources: github.com/postgres, Lobsters