importccl: fix case sensitive INSERT INTO column names in PGDUMP #52485
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.
Refs: #52382
Tested by uncommenting out the skip and re-commenting it afterwards.
Release note (sql change, bug fix): When using
IMPORT PGDUMP
withINSERT INTO
clauses, specifying a column name that is case sensitive(e.g.
"cApItAls"
) would previously error specifying the column namewas not found. This has been rectified.