PostgreSQL: parse ALTER TRIGGER RENAME TO and DEPENDS ON EXTENSION - #2430
Open
LucaCappelletti94 wants to merge 1 commit into
Open
PostgreSQL: parse ALTER TRIGGER RENAME TO and DEPENDS ON EXTENSION#2430LucaCappelletti94 wants to merge 1 commit into
ALTER TRIGGER RENAME TO and DEPENDS ON EXTENSION#2430LucaCappelletti94 wants to merge 1 commit into
Conversation
LucaCappelletti94
marked this pull request as ready for review
August 5, 2026 15:37
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.
ALTER TRIGGER tr ON t RENAME TO tqdid not parse in any dialect, becauseTRIGGERwas not among the object typesparse_alteraccepted.PostgreSQL's grammar has exactly two forms, so
AlterTriggerOperationcoversRENAME TOand[ NO ] DEPENDS ON EXTENSION, the second reusing the shapeAlterFunctionOperation::DependsOnExtensionalready provides for that same clause.