Re: CLUSTER progress: wrong index_rebuild_count for tables with TOAST

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Adam Lee <adam8157(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, alvherre(at)kurilemu(dot)de
Subject: Re: CLUSTER progress: wrong index_rebuild_count for tables with TOAST
Date: 2026-06-26 15:23:53
Message-ID: 78277.1782487433@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Adam Lee <adam8157(at)gmail(dot)com> wrote:

> The reason is that make_new_heap() creates the new TOAST table, and its
> TOAST index, before the heap is scanned. Building that index reports
> CREATE INDEX progress. CREATE INDEX and the cluster command use the same
> progress field for different things, so the cluster command then shows a
> CREATE INDEX value as its index_rebuild_count.

I'd prefer enhanced progress monitoring that I proposed earlier [1]. The patch
needs more work, I'll try to submit it for the next development cycle.

[1] https://www.postgresql.org/message-id/30939.1777888333%40localhost

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-06-26 15:49:48 Re: [GSoC 2026] - B-tree Index Bloat Reduction - Approach & Questions
Previous Message Dmitry Koval 2026-06-26 15:20:18 Re: Add SPLIT PARTITION/MERGE PARTITIONS commands