Make query compatible with postgres 19 - #783
Open
docteurklein wants to merge 1 commit into
Open
Conversation
postgres 19beta1 introduces a new column `location` in the `pg_available_extensions` view. But because its columns are referenced positionally, it breaks this query in 19. Here is a fix that works on both 18 and 19.
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.
postgres 19beta1 introduces a new column
locationin thepg_available_extensionsview. https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=f3c9e341cBut because its columns are referenced positionally, it breaks this query in 19. Here is a fix that works on both 18 and 19.
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
✖ Database error: column reference "comment" is ambiguous
and
"cannot connect to database"