Fix for retrieving column metadata for Postgres < 10#6438
Merged
roji merged 1 commit intonpgsql:mainfrom Feb 7, 2026
Merged
Conversation
Contributor
Author
|
@roji, Should I create a pull request to the 9 and 10 version branches? |
Member
|
Backported to 10.0.2 via ea5c131 |
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.
I maintain a system that runs Greenplum 6 (PG 9).
After changing 450f900 , retrieving metadata returns the following error:
In this case the following SQL is generated:
I checked that the information_schema.columns attribute in postgres 9 can be updated without the attribute identity.
After the change, retrieving metadata works correctly.
This error is repeated in versions 9 and 10.