| From: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, alvherre(at)alvh(dot)no-ip(dot)org, Mihail Nikalayeu <mihailnikalayeu(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-03-24 12:13:41 |
| Message-ID: | 8541283e-3d72-41f7-b6ee-b1655ceb6c7a@uni-muenster.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 24/03/2026 09:48, Antonin Houska wrote:
> Thanks for the report. I agree that there's no reason for REPACK to get
> blocked on a lock of a table that it will not process anyway. However, as both
> VACUUM FULL and CLUSTER in PG 18 appear to have the same problem, I'm not sure
> your patch needs to be incorporated in the new feature. Adding a bug fix entry
> to the CF seems the appropriate action to me.
Indeed. VACUUM FULL seems to have the same problem.
I'll include it in the patch and open a new thread.
Best, Jim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2026-03-24 12:13:43 | Re: [Proposal] Adding Log File Capability to pg_createsubscriber |
| Previous Message | Lakshmi N | 2026-03-24 12:07:40 | Re: log XLogPrefetch stats at end of recovery |