Re: Adding REPACK [concurrently]

On 2026-Feb-01, Mihail Nikalayeu wrote:

> Also, I am still not sure if MVCC-safe implementation is worth
> its complexity compared with "relcheckxmin"approach [0].

I'm not sure it's acceptable to cause other sessions to raise errors if
they query the table being repacked (or a table repacked recently).
That sounds extremely unpleasant.  Imagine a long-running transactions
that runs enormous queries for many hours or even days, being killed
near the end because some DBA decided to run REPACK on a table.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/