aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2021-08-17 10:00:06 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2021-08-17 11:17:59 +0300
commit9454265eb26ac87e71f4af5853281fa166f55b79 (patch)
tree451d30485dcee45ac30ebe720297d64fa43603e2
parent84c1bac579db605e6a7d7b15f7f641c583d7e6e9 (diff)
downloadpostgresql-9454265eb26ac87e71f4af5853281fa166f55b79.tar.gz
postgresql-9454265eb26ac87e71f4af5853281fa166f55b79.zip
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
-rw-r--r--doc/src/sgml/ref/copy.sgml10
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 4c1e7dfef32..718bf477aeb 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -628,12 +628,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>
@@ -666,6 +666,12 @@ COPY <replaceable class="parameter">count</replaceable>
</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
output carriage return/newline (<quote><literal>\r\n</literal></quote>), but only for