TableAmRoutine's index_build_range_scan thinks that parameter #8 is
called end_blockno, but table_index_build_range_scan and
heapam_index_build_range_scan and BRIN's summarize_range all agree
that it's the number of blocks to be scanned.  I assume that this got
changed at some point while Andres was hacking on it and this one
place just never got updated.

Proposed patch attached.  Since this seems like a bug, albeit a
harmless one, I propose to commit this to v12.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment: 0001-tableam-Fix-index_build_range_scan-parameter-name.patch
Description: Binary data

Reply via email to