Re: CLUSTER progress: wrong index_rebuild_count for tables with TOAST

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Adam Lee <adam8157(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Antonin Houska <ah(at)cybertec(dot)at>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Subject: Re: CLUSTER progress: wrong index_rebuild_count for tables with TOAST
Date: 2026-08-27 16:01:57
Message-ID: apBfdVNriIEN-RPO@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 26, 2026 at 02:45:57PM +0800, Adam Lee wrote:
> When I run CLUSTER (or VACUUM FULL / REPACK) on a table that has a TOAST
> table, pg_stat_progress_cluster shows a wrong index_rebuild_count. During
> the heap scan the count is already equal to the number of indexes, but it
> should be 0 until the indexes are rebuilt at the end.

Hm. Isn't this a regression in v19 caused by commit 28d534e?

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-08-27 16:09:59 Re: REPACK (ANALYZE) within transaction block segfaults
Previous Message Nathan Bossart 2026-08-27 15:56:08 Re: pg_plan_advice: fix empty FOREIGN_JOIN sublist validation