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
- Re: Adding REPACK [con... Antonin Houska
- Re: Adding REPACK [con... Antonin Houska
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Alvaro Herrera
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Jim Jones
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently... Jim Jones
- Re: Adding REPACK [concurrently] Srinath Reddy Sadipiralla
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Antonin Houska
- Re: Adding REPACK [concurrently] Srinath Reddy Sadipiralla
- Re: Adding REPACK [concurrently] Srinath Reddy Sadipiralla
- Re: Adding REPACK [concurrently] Alvaro Herrera
- Re: Adding REPACK [concurrently] Srinath Reddy Sadipiralla
- Re: Adding REPACK [concurrently... Srinath Reddy Sadipiralla
- Re: Adding REPACK [concurr... Alvaro Herrera
- Re: Adding REPACK [con... Srinath Reddy Sadipiralla
