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 <[email protected]> Discussion: https://postgr.es/m/[email protected] 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(+)
