pg16 blocker - Update pg_stat_monitor #1211
Closed
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.
Updates pg_stat_monitor from 1.1.1 to 2.1.0
This is necessary for pg16 support
The vast majority of the massive diff is whitespace due to much of the data being in table and the column size grew. I'll figure out how to address this properly in a later PR.
Here is the actual diff ignoring whitespace. It does include breaking changes, however it would not be common practice to e.g. create views on top of pg_stat_monitor in a way that would break during the upgrade process, but there is some risk