Merged
Conversation
ghost
mentioned this pull request
Collaborator
|
Thanks! Looks like this was surprisingly simple to achieve. |
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.
The
pg_dumpclients shipped with PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 began wrapping plain-text dump scripts in\restrict <key>and\unrestrict <key>guards. sql-formatter 15.7.0 rejects these scripts at the opening guard.pg_dumpalland SQL scripts generated bypg_restore --fileuse the same guards.This change recognizes the
\restrictand\unrestrictprefixes as opaque line directives. It preserves each generated key, formats the enclosed SQL, and leaves other psql meta-commands unsupported.Fixes #935