Removing unnecessary backslashes and whitespace from postgres script. #467
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.
In EL9 (Rocky Linux 9 in my case), awk complains that "escaping" semi-colons is not a known regexp operator:
It looks like the backslashes are unnecessary. After the change, the script no longer complains:
I also tested this change on an older CentOS Stream 8 deployment (that was not throwing the same warning) and there were no issues after the fact: