Fwd: Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option

From: Jochen Bandhauer <jb(at)jbitc(dot)de>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Fwd: Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option
Date: 2026-08-26 07:18:35
Message-ID: 8c1acba6-7f7d-4daa-a43a-9bedaf078339@jbitc.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 26.08.2026 02:44, Fujii Masao wrote:
> On Wed, Aug 26, 2026 at 6:00 AM Jochen Bandhauer <jb(at)jbitc(dot)de> wrote:
>> Am 25. August 2026 21:57:44 MESZ schrieb Nathan Bossart
>> <nathandbossart(at)gmail(dot)com>:
>>> Does this one deserve a mention on the open items wiki [0]?
>>>
>>> [0] https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items
>>>
>> I think yes. It's not critical to the functionality, but the verbose
>> output is not correct.
> I agree that this should be fixed, but I wonder whether this is entirely
> new in v19.
>
> AFAICS, the same kind of misleading "removable" count can also occur with
> CLUSTER USING INDEX in v18 and older releases, since the count depends
> on the scan path. The CONCURRENTLY case is new, but the USING INDEX
> case does not seem to be.
>
> So I'm not sure this should be considered a v19 blocker. Perhaps
> documenting this limitation for now would be sufficient?
>
> Regards,
>
All you said is correct, and it should not be considered a v19 blocker.
If the Open Items list only contains v19 blockers, then it shouldn't be
there (as opposed to what I said earlier).

Jochen

Attachment Content-Type Size
jb.vcf text/vcard 202 bytes

Browse pgsql-bugs by date

  From Date Subject
Next Message Zsolt Parragi 2026-08-26 07:31:32 Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Previous Message Kyotaro Horiguchi 2026-08-26 06:28:41 Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes