pg_stat_statements: Add rows_scanned and rows_filtered columns #5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pg_stat_statements: Add rows_scanned and rows_filtered columns
Summary
This PR adds two new columns to
pg_stat_statementsto help identify queries that may benefit from better indexing:rows_scanned- Total rows fetched from storage by scan nodes before any filteringrows_filtered- Total rows removed by filter conditions (scanqual, joinqual, and other quals)These metrics are useful for identifying inefficient queries that scan many rows but return few results.
Implementation Details
INSTRUMENT_ALL) inExecutorStarthookExecutorEndto collect statistics from all nodesrows_scanned: sums tuples from scan nodes (SeqScan, IndexScan, etc.) including filtered tuplesrows_filtered: sumsnfiltered1(scanqual/joinqual) andnfiltered2(other quals) from all nodesntuplesandtuplecountfrom instrumentation to capture complete tuple countsExample Output