Re: REPACK (CONCURRENTLY) can't complete after ~105M concurrent updates/deletes

On Thu, Oct 08, 2026 at 02:34:50PM +0200, Alvaro Herrera wrote:
> On 2026-Oct-08, Radim Marek wrote:
>> As a medium-heavy repack user over the last decade, I'd say this limit is
>> acceptable for now.
>
> Agreed -- I don't think we need any localized hacking for this,
> considering that we have a patch in the queue for 20 that will
> completely remove the need for this. People that can't tolerate 105
> million rows concurrently updated during REPACK (CONCURRENTLY) can do
> whatever they've been doing so far to cope with such a scenario. Maybe
> they run pg_repack, or maybe they run VACUUM FULL, I don't really care.
> (What I actually think is that such people don't actually exist.)
>
> IMO this is not a regression and we don't *need* to cope with it.

Okay. It sounds like we have carefully considered this behavior and deemed
it acceptable for now, and I do not intend to press the issue any further.
Thanks!

--
nathan