Peter Geoghegan 0fbceae841 Show index search count in EXPLAIN ANALYZE, take 2. ... Expose the count of index searches/index descents in EXPLAIN ANALYZE's output for index scan/index-only scan/bitmap index scan nodes. This information is particularly useful with scans that use ScalarArrayOp quals, where the number of index searches can be unpredictable due to implementation details that interact with physical index characteristics (at least with nbtree SAOP scans, since Postgres 17 commit 5bf748b8). The information shown also provides useful context when EXPLAIN ANALYZE runs a plan with an index scan node that successfully applied the skip scan optimization (set to be added to nbtree by an upcoming patch). The instrumentation works by teaching all index AMs to increment a new nsearches counter whenever a new index search begins. The counter is incremented at exactly the same point that index AMs already increment the pg_stat_*_indexes.idx_scan counter (we're counting the same event, but at the scan level rather than the relation level). Parallel queries have workers copy their local counter struct into shared memory when an index scan node ends -- even when it isn't a parallel aware scan node. An earlier version of this patch that only worked with parallel aware scans became commit 5ead85fb (though that was quickly reverted by commit d00107cd following "debug_parallel_query=regress" buildfarm failures). Our approach doesn't match the approach used when tracking other index scan related costs (e.g., "Rows Removed by Filter:"). It is comparable to the approach used in similar cases involving costs that are only readily accessible inside an access method, not from the executor proper (e.g., "Heap Blocks:" output for a Bitmap Heap Scan, which was recently enhanced to show per-worker costs by commit 5a1e6df3, using essentially the same scheme as the one used here). It is necessary for index AMs to have direct responsibility for maintaining the new counter, since the counter might need to be incremented multiple times per amgettuple call (or per amgetbitmap call). But it is also necessary for the executor proper to manage the shared memory now used to transfer each worker's counter struct to the leader. Author: Peter Geoghegan <pg@bowt.ie> Reviewed-By: Robert Haas <robertmhaas@gmail.com> Reviewed-By: Tomas Vondra <tomas@vondra.me> Reviewed-By: Masahiro Ikeda <ikedamsh@oss.nttdata.com> Reviewed-By: Matthias van de Meent <boekewurm+postgres@gmail.com> Discussion: https://postgr.es/m/CAH2-WzkRqvaqR2CTNqTZP0z6FuL4-3ED6eQB0yx38XBNj1v-4Q@mail.gmail.com Discussion: https://postgr.es/m/CAH2-Wz=PKR6rB7qbx+Vnd7eqeB5VTcrW=iJvAsTsKbdG+kW_UA@mail.gmail.com		2025-03-11 09:20:50 -04:00
..
expected	Remove incidental md5() function uses from several tests	2023-07-04 14:31:57 +02:00
sql	Remove incidental md5() function uses from several tests	2023-07-04 14:31:57 +02:00
t	Update copyright for 2025	2025-01-01 11:21:55 -05:00
.gitignore
blcost.c	Update copyright for 2025	2025-01-01 11:21:55 -05:00
blinsert.c	Update copyright for 2025	2025-01-01 11:21:55 -05:00
bloom--1.0.sql	Minor fixes in contrib installation scripts.	2016-06-14 10:47:06 -04:00
bloom.control
bloom.h	Update copyright for 2025	2025-01-01 11:21:55 -05:00
blscan.c	Show index search count in EXPLAIN ANALYZE, take 2.	2025-03-11 09:20:50 -04:00
blutils.c	Rename amcancrosscompare	2025-03-07 11:46:33 +01:00
blvacuum.c	Add is_analyze parameter to vacuum_delay_point().	2025-02-11 16:38:14 -06:00
blvalidate.c	Add get_opfamily_name() function	2025-02-01 10:42:58 +01:00
Makefile	Re-enable contrib/bloom's TAP tests.	2021-09-27 18:48:01 -04:00
meson.build	Update copyright for 2025	2025-01-01 11:21:55 -05:00