Cherry-pick: Add pg_buffercache_usage_counts() to contrib/pg_buffercache. #1492
+177
−24
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.
Turns out,
CREATE EXTENSION pg_buffercachedoes not work on main.It is failing due pg_buffercache_usage_counts function is missing.
This function was committed to PostgreSQL as part of postgres/postgres@f3fa313
Extension sql 1.4.1 version was cherry-picked to Cloudberry as part of #883 (see commit 79f2d28)
This pr fixes cherry-pick issues, and adds this extension to
ic-contribcheckFound during PG16 rebase work
Original commit msg:
It was pointed out that pg_buffercache_summary()'s report of the overall average usage count isn't that useful, and what would be more helpful in many cases is to report totals for each possible usage count. Add a new function to do it like that. Since pg_buffercache 1.4 is already new for v16, we don't need to create a new extension version; we'll just define this as part of 1.4.
Nathan Bossart
Discussion: https://postgr.es/m/20230130233040.GA2800702@nathanxps13