Fix PostgreSQL 18 compatibility issues related to "?column?" names in… #8090
+833
−16
Conversation
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
… subqueries - Updated various planner and deparser files to handle NULL or "?column?" as resname by generating meaningful column names. - Ensured that generated names follow a consistent format to avoid parsing errors in complex queries. - Added debug queries and tests to isolate and reproduce the issues related to intermediate results and subqueries. - Created setup scripts for test tables and data to facilitate regression testing for PostgreSQL 18 compatibility.
|
@microsoft-github-policy-service agree [company="{gurkan}"] |
|
@gurkanindibay the command you issued was incorrect. Please try again. Examples are: and |
|
@microsoft-github-policy-service agree company="Gürkan" |
|
Thanks for your support. Would you be able to identify the PostgreSQL commit that introduced this behavior? |
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.
… subqueries
DESCRIPTION: PR description that will go into the change log, up to 78 characters