Re: Adding REPACK [concurrently] - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: Adding REPACK [concurrently]
Date
Msg-id CADzfLwWr-SQyVLkOryKpkL3yYLokuq2o-M3Ku1_XZrZMvxeWwg@mail.gmail.com
Whole thread
In response to Re: Adding REPACK [concurrently]  (Antonin Houska <ah@cybertec.at>)
Responses Re: Adding REPACK [concurrently]
List pgsql-hackers
Hello!

On Thu, Apr 9, 2026 at 11:26 AM Antonin Houska <ah@cybertec.at> wrote:
> Sure, it's possible, but IMO the principal question is whether REPACK should
> let VACUUM and DDLs error out, or just let them wait.

One more idea: instead of ERROR in CheckTableNotInUse in case of
in_repack - just release the lock and retry a little later (by that
time, the repack operation will likely have acquired the AEL).



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Add errdetail() with PID and UID about source of termination signal
Next
From: Andres Freund
Date:
Subject: Re: Adding REPACK [concurrently]