Fix: ENR temp table creation fails for long table names#769
Open
anju15bharti wants to merge 3 commits into
Open
Fix: ENR temp table creation fails for long table names#769anju15bharti wants to merge 3 commits into
anju15bharti wants to merge 3 commits into
Conversation
1 task
ayushdsh
reviewed
Jun 9, 2026
ayushdsh
reviewed
Jun 9, 2026
Contributor
|
/code-review |
added 2 commits
June 9, 2026 13:35
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.
Description
Temp tables with names longer than 63 characters were erroring out because the name was clipped before storing in ENR. Pass the full name to ENR during creation, and use the full ENR name in ALTER TABLE when rebuilding the RangeVar.
Issues Resolved
BABEL-6433
Extension PR : babelfish-for-postgresql/babelfish_extensions#4846
Check List
By submitting this pull request, I confirm that my contribution is under the terms of the PostgreSQL license, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.