pgsql: Count the last block of the validation scan in a concurrent inde

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Count the last block of the validation scan in a concurrent inde
Date: 2026-10-27 03:25:12
Message-ID: E1xLXoG-00000000vGG-0BEB@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Count the last block of the validation scan in a concurrent index build

heapam_index_validate_scan() reports PROGRESS_SCAN_BLOCKS_DONE as the
number of the block that the scan starts on, forgetting to count the
last block scanned.

Due to the last block not being counted, the number of blocks_done never
matched blocks_total. This information could remain on the view for a
long time, depending on the waits done between the phases of CREATE
INDEX CONCURRENTLY or REINDEX CONCURRENTLY.

This is incorrect still purely cosmetic, so no backpatch is done.

Author: Manu <manuelreyesbravo(at)gmail(dot)com>
Discussion: https://postgr.es/m/179303526069.2212386.7608335332316408826@gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/99ea4a55270d5ce48bc33b9daf5d641818e03b89

Modified Files
--------------
src/backend/access/heap/heapam_handler.c | 4 ++++
1 file changed, 4 insertions(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2026-10-27 04:56:38 pgsql: Avoid truncated or zero-padded copies of replaced files in backu
Previous Message Bruce Momjian 2026-10-27 03:19:24 pgsql: doc PG 19 relnotes: mention when ALTER SUBSCRIPTION affects item