pg_stat_monitor with a logging backend #1801
Draft
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
|
@olirice what's a good way to test this extension in your view? I can help implement if needed |
|
lets wait for feedback from @kemaldotearth before writing any tests. the implementation may have to change at this point I think
|
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.
Adds a low memory configuration for pg_stat_monitor + a logging backend to durably drive query insights.
this PR is to cut a staging image for experimentation. its in draft
Note that
supabase/infrastructurespecifically strip pg_stat_monitor from shared preloads due to a previous issue, so to test you need to manually ssh in to the staging instance, update postgresql.conf, and then restart postgres