diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-27 19:42:42 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-08-27 19:42:42 -0400 |
| commit | 187b5fea982e6fd56a0311ca9f899f792307e534 (patch) | |
| tree | db21202d098b922c98363391d2d11713e05adb22 /src/backend/commands/tablespace.c | |
| parent | 38ed1566ee3417319f39ae7fb8a3fb55d9b26eeb (diff) | |
| download | postgresql-187b5fea982e6fd56a0311ca9f899f792307e534.tar.gz postgresql-187b5fea982e6fd56a0311ca9f899f792307e534.zip | |
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
Diffstat (limited to 'src/backend/commands/tablespace.c')
0 files changed, 0 insertions, 0 deletions