Skip standard_conforming_strings=off on PG19#2506
Merged
Merged
Conversation
For the same security reason why standard_conforming_strings=off is disallowed by pgx in combination with the simple query protocol, in PG19 standard_conforming_strings=off won't be allowed anymore at all. See: postgres/postgres@4576208
Contributor
Author
|
To clarify, I ran into this while running pgx tests against a local postgres server that was build from the postgres master branch. |
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.
For the same security reason why
standard_conforming_strings=offis disallowed by pgx in combination with the simple query protocol, in PG19standard_conforming_strings=offwon't be allowed anymore at all.See this for details: postgres/postgres@4576208