PostgreSQL: Allow non-reserved keywords as table aliases - #2479
Merged
Conversation
BenSatori
force-pushed
the
postgres-allowed-table-aliases
branch
from
September 2, 2026 19:11
7fa5e29 to
6489ee9
Compare
yoavcloud
approved these changes
Sep 3, 2026
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
2 participants
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.
Allow PostgreSQL keywords that are non-reserved there to be used as table aliases.
For example:
SELECT * FROM tbl_name AS start
JOIN tbl_name_2 ON start.id = tbl_name_2.id
Added PostgreSQL regression coverage for the supported aliases.