I wonder how understanding pg_stat_all_indexes working
When I run an explain, some index are not used, but pg_stat_all_indexes.idx_scan is incremented for those indexes.
When the planner considers using a merge join on a indexed column, it uses an index to check the endpoints of the column (the min and the max) to make sure it has the latest values to get the most accurate estimate. This causes the usage counts to get incremented. Even when it doesn't end up using the merge join.
Does this mean idx_scan is incremented each time the planner check if an index could be use whenever it won't use it ?
From:
"Graeme B. Bell" Date: Subject:
Re: Hmmm... why does CPU-intensive pl/pgsql code
parallelise so badly when queries parallelise fine? Anyone else seen this?
