Fallback for db_exists when the pg_catalog is protected #57
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
sbidoul
force-pushed
the
catalog-privileges
branch
from
fbb4e9a to
71895a0
Compare
sbidoul
force-pushed
the
catalog-privileges
branch
from
71895a0 to
fd1fb91
Compare
legalsylvain
approved these changes
Oct 13, 2025
Contributor
legalsylvain
left a comment
legalsylvain
left a comment
There was a problem hiding this comment.
hi. Code review / no test. Thanks !
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.
In some situations access
pg_catalog.pg_databasesis restricted.Implement a fallback for
db_existsby checking if we can connect.