| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Jochen Bandhauer <jb(at)jbitc(dot)de> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option |
| Date: | 2026-08-26 00:44:08 |
| Message-ID: | CAHGQGwEQrRSV3Jax-91hWAzxFb_CkqSg5duvY+PEjhgvCXCUjg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-08-26 00:50:24 | Re: BUG #19637: pg_event_trigger_ddl_commands can't process GRANT ON PROPERTY GRAPH |
| Previous Message | Jochen Bandhauer | 2026-08-25 21:00:16 | Re: repack with verbose output: not showing the number of removable row versions when using USING INDEX or CONCURRENTLY option |