| From: | Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net> |
| Subject: | Re: Adding REPACK [concurrently] |
| Date: | 2026-04-09 14:06:17 |
| Message-ID: | CADzfLwWr-SQyVLkOryKpkL3yYLokuq2o-M3Ku1_XZrZMvxeWwg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello!
On Thu, Apr 9, 2026 at 11:26 AM Antonin Houska <ah(at)cybertec(dot)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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-04-09 14:13:26 | Re: Adding REPACK [concurrently] |
| Previous Message | Andres Freund | 2026-04-09 14:00:32 | Re: Add errdetail() with PID and UID about source of termination signal |