Skip to content

Commit c444472

Browse files
committed
Fix backslash-escaping multibyte chars in COPY FROM.
If a multi-byte character is escaped with a backslash in TEXT mode input, and the encoding is one of the client-only encodings where the bytes after the first one can have an ASCII byte "embedded" in the char, we didn't skip the character correctly. After a backslash, we only skipped the first byte of the next character, so if it was a multi-byte character, we would try to process its second byte as if it was a separate character. If it was one of the characters with special meaning, like '\n', '\r', or another '\\', that would cause trouble. One such exmple is the byte sequence '\x5ca45c2e666f6f' in Big5 encoding. That's supposed to be [backslash][two-byte character][.][f][o][o], but because the second byte of the two-byte character is 0x5c, we incorrectly treat it as another backslash. And because the next character is a dot, we parse it as end-of-copy marker, and throw an "end-of-copy marker corrupt" error. Backpatch to all supported versions. Reviewed-by: John Naylor, Kyotaro Horiguchi Discussion: https://www.postgresql.org/message-id/a897f84f-8dca-8798-3139-07da5bb38728%40iki.fi
1 parent 5e7fa18 commit c444472

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

src/backend/commands/copyfromparse.c

+9-1
Original file line numberDiff line numberDiff line change
@@ -1084,7 +1084,7 @@ CopyReadLineText(CopyFromState cstate)
10841084
break;
10851085
}
10861086
else if (!cstate->opts.csv_mode)
1087-
1087+
{
10881088
/*
10891089
* If we are here, it means we found a backslash followed by
10901090
* something other than a period. In non-CSV mode, anything
@@ -1095,8 +1095,16 @@ CopyReadLineText(CopyFromState cstate)
10951095
* backslashes are not special, so we want to process the
10961096
* character after the backslash just like a normal character,
10971097
* so we don't increment in those cases.
1098+
*
1099+
* Set 'c' to skip whole character correctly in multi-byte
1100+
* encodings. If we don't have the whole character in the
1101+
* buffer yet, we might loop back to process it, after all,
1102+
* but that's OK because multi-byte characters cannot have any
1103+
* special meaning.
10981104
*/
10991105
raw_buf_ptr++;
1106+
c = c2;
1107+
}
11001108
}
11011109

11021110
/*

0 commit comments

Comments
 (0)