diff options
| author | Tom Lane | 2024-04-06 15:16:27 +0000 |
|---|---|---|
| committer | Tom Lane | 2024-04-06 15:16:27 +0000 |
| commit | ddd9e43a92417dd0c2b60822d6e75862c73b139a (patch) | |
| tree | fb351c91e90f9717362eb212e0772ba84510d516 | |
| parent | a365d9e2e8c1ead27203a4431211098292777d3b (diff) | |
Remove obsolete comment in CopyReadLineText().
When this bit of commentary was written, it was alluding to the
fact that we looked for newlines and EOD markers in the raw
(not yet encoding-converted) input data. We don't do that anymore,
preferring to batch the conversion of larger chunks of input and
split it into lines later. Hence there's no longer any need for
assumptions about the relevant characters being encoding-invariant,
and we should remove this comment saying we assume that.
Discussion: https://postgr.es/m/[email protected]
| -rw-r--r-- | src/backend/commands/copyfromparse.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/backend/commands/copyfromparse.c b/src/backend/commands/copyfromparse.c index 7ddd27f5c6..7efcb89159 100644 --- a/src/backend/commands/copyfromparse.c +++ b/src/backend/commands/copyfromparse.c @@ -1206,9 +1206,6 @@ CopyReadLineText(CopyFromState cstate) * value and are put in line_buf. We keep just enough state to know if we * are currently in a quoted field or not. * - * These four characters, and the CSV escape and quote characters, are - * assumed the same in frontend and backend encodings. - * * The input has already been converted to the database encoding. All * supported server encodings have the property that all bytes in a * multi-byte sequence have the high bit set, so a multibyte character |