Count SP-GiST index scans in pg_stat statistics.
authorTom Lane <[email protected]>
Fri, 27 Aug 2021 23:42:42 +0000 (19:42 -0400)
committerTom Lane <[email protected]>
Fri, 27 Aug 2021 23:42:42 +0000 (19:42 -0400)
commit6a787c83c48a4d87d5aaa57776015ab77934d0ce
tree2ae8569283d45bf36565e9a74e217a2f3a4960d6
parent7c8f2c77108dd569f7fba3b42ca4e9f2452647ab
Count SP-GiST index scans in pg_stat statistics.

Somehow, spgist overlooked the need to call pgstat_count_index_scan().
Hence, pg_stat_all_indexes.idx_scan and equivalent columns never
became nonzero for an SP-GiST index, although the related per-tuple
counters worked fine.

This fix works a bit differently from other index AMs, in that the
counter increment occurs in spgrescan not spggettuple/spggetbitmap.
It looks like this won't make the user-visible semantics noticeably
different, so I won't go to the trouble of introducing an is-this-
the-first-call flag just to make the counter bumps happen in the
same places.

Per bug #17163 from Christian Quest.  Back-patch to all supported
versions.

Discussion: https://postgr.es/m/17163-b8c5cc88322a5e92@postgresql.org
src/backend/access/spgist/spgscan.c