Pull latest pg_dump, Sanity check and code#320
Merged
Conversation
REVOKE ALL from _pgactive_node_name_present_private for PUBLIC Add a new test to detect if any of the privatye functions are exposed to PUBLIC Don't start perdb wrokers if pgactive schema is present in DB but extension is not yet created. Add 2.1.8 sqls
Fix tests to use events instead of random sleeps
Fix more edge cases in testintg
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Pull latest pg_dump codes
REVOKE ALL from _pgactive_node_name_present_private for PUBLIC
Add a new test to detect if any of the privatye functions are exposed to PUBLIC
Don't start perdb wrokers if pgactive schema is present in DB but extension is not yet created.
Support libzstd when postgres was compiled against zstd.