postgres.git / summary / log / commit / refs

commit    f90c05959ec3fb712cba889817e0a0689fa6fa89
Author:   Heikki Linnakangas <heikki.linnakangas@iki.fi>
Date:     Tue Aug 17 07:00:06 2021 +0000
First released in: 15.0, 9.6.24, 10.19, 11.14, 12.9, 13.5, 14.0

    doc: \123 and \x12 escapes in COPY are in database encoding.
    
    The backslash sequences, including \123 and \x12 escapes, are interpreted
    after encoding conversion. The docs failed to mention that.
    
    Backpatch to all supported versions.
    
    Reported-by: Andreas Grob
    Discussion: https://www.postgresql.org/message-id/17142-9181542ca1df75ab%40postgresql.org


doc/src/sgml/ref/copy.sgml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index 14cd437da0a..4624c8f4c98 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -636,12 +636,12 @@ COPY <replaceable class="parameter">count</replaceable> <row> <entry><literal>\</literal><replaceable>digits</replaceable></entry> <entry>Backslash followed by one to three octal digits specifies - the character with that numeric code</entry> + the byte with that numeric code</entry> </row> <row> <entry><literal>\x</literal><replaceable>digits</replaceable></entry> <entry>Backslash <literal>x</literal> followed by one or two hex digits specifies - the character with that numeric code</entry> + the byte with that numeric code</entry> </row> </tbody> </tgroup> @@ -673,6 +673,12 @@ COPY <replaceable class="parameter">count</replaceable> or vice versa). </para> + <para> + All backslash sequences are interpreted after encoding conversion. + The bytes specified with the octal and hex-digit backslash sequences must + form valid characters in the database encoding. + </para> + <para> <command>COPY TO</command> will terminate each row with a Unix-style newline (<quote><literal>\n</literal></quote>). Servers running on Microsoft Windows instead [parent: b3d24cc0f0aa]