pg_stat_statements_info: Add gc_count and query_file_size #9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This surfaces two internal fields from pg_stat_statements in the pg_stat_statements_info view to help with debugging. "gc_count" helps understand when there are significant numbers of deallocations causing I/O overhead due to query text file rewrites. "query_file_size" can be used to determine the query text file size without actually reading the file, e.g. for use in monitoring queries, or when deciding how often to get pg_stat_statements data with query texts.
lfittl
force-pushed
the
pgss-additional-info
branch
from
ed818f1 to
e327cf7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This surfaces two internal fields from pg_stat_statements in the pg_stat_statements_info view to help with debugging.
"gc_count" helps understand when there are significant numbers of deallocations causing I/O overhead due to query text file rewrites.
"query_file_size" can be used to determine the query text file size without actually reading the file, e.g. for use in monitoring queries, or when deciding how often to get pg_stat_statements data with query texts.