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

From Jim Jones
Subject Re: Adding REPACK [concurrently]
Date
Msg-id 8541283e-3d72-41f7-b6ee-b1655ceb6c7a@uni-muenster.de
Whole thread Raw
In response to Re: Adding REPACK [concurrently]  (Antonin Houska <ah@cybertec.at>)
List 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



pgsql-hackers by date:

Previous
From: Lakshmi N
Date:
Subject: Re: log XLogPrefetch stats at end of recovery
Next
From: Amit Kapila
Date:
Subject: Re: [Proposal] Adding Log File Capability to pg_createsubscriber