Disable postgres USER triggers #299
Merged
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
To be able to disable ALL triggers on a database, one needs a user that can disable system triggers.
|
@gforcada I am not a PG user here. So in theory, I am ok with the change. |
avelis
approved these changes
Aug 15, 2018
|
Thanks @gforcada, the patch from |
|
@avelis could we get a release? TIA! 👍 |
|
@gforcada Let me see what I can do. I appreciate the patience and all the contributions this library gets. |
|
Hi! any news about a possible release? I'm getting impacted by this as well. 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.
To be able to disable ALL triggers on a database, one needs a user that can disable system triggers.
Should fix #290