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 | |
| 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
| -rw-r--r-- | src/backend/access/spgist/spgscan.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/backend/access/spgist/spgscan.c b/src/backend/access/spgist/spgscan.c index dbd68a3b24c..f216fba5294 100644 --- a/src/backend/access/spgist/spgscan.c +++ b/src/backend/access/spgist/spgscan.c @@ -19,6 +19,7 @@ #include "access/relscan.h" #include "access/spgist_private.h" #include "miscadmin.h" +#include "pgstat.h" #include "storage/bufmgr.h" #include "utils/datum.h" #include "utils/float.h" @@ -410,6 +411,9 @@ spgrescan(IndexScanDesc scan, ScanKey scankey, int nscankeys, /* set up starting queue entries */ resetSpGistScanOpaque(so); + + /* count an indexscan for stats */ + pgstat_count_index_scan(scan->indexRelation); } void |