Database: avoid LEAKPROOF since it requires superuser privileges #723
Conversation
This file contains 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
Avoid using LEAKPROOF for database functions because it requires superuser privileges and most installations don't use privileged database users for connecting to Postgres, for example in production environments. Signed-off-by: Davide Briani <[email protected]>
noaccOS
approved these changes
Nov 15, 2024
Pull Request Test Coverage Report for Build e3d722ca875eb1fa8cd9585f348a8f5e4caa40df-PR-723Details
💛 - Coveralls |
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.
Avoid using LEAKPROOF for database functions because it requires superuser privileges and most installations don't use privileged database users for connecting to Postgres, for example in production environments.