Message-ID: <8541283e-3d72-41f7-b6ee-b1655ceb6c7a@uni-muenster.de>
Date: Tue, 24 Mar 2026 13:13:41 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Adding REPACK [concurrently]
To: Antonin Houska <ah@cybertec.at>
Cc: Srinath Reddy Sadipiralla <srinath2133@gmail.com>,
 alvherre@alvh.no-ip.org, Mihail Nikalayeu <mihailnikalayeu@gmail.com>,
 Pg Hackers <pgsql-hackers@lists.postgresql.org>,
 Robert Treat <rob@xzilla.net>
References: <202602241757.6ac3iss2u4vo@alvherre.pgsql>
 <9116.1772009759@localhost>
 <CAFC+b6o2yzA80YmfEhmMO9puN8qvGRvr-15BBLn3UmJxPfpr2w@mail.gmail.com>
 <100248.1772048475@localhost> <4200.1772781295@localhost>
 <29157.1774029970@localhost> <46846.1774267234@localhost>
 <713021dd-bf6c-407a-8c9d-f79ecbd1c2ee@uni-muenster.de>
 <13637.1774342137@localhost>
Content-Language: de-DE, en-GB
From: Jim Jones <jim.jones@uni-muenster.de>
In-Reply-To: <13637.1774342137@localhost>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/8541283e-3d72-41f7-b6ee-b1655ceb6c7a%40uni-muenster.de>
Precedence: bulk


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