Commitc9e75c2

committed

doc: \123 and \x12 escapes in COPY are in database encoding.

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

1 parent7f0873f commitc9e75c2Copy full SHA for c9e75c2

File tree

-2

lines changed

-2

lines changed

Lines changed: 8 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -628,12 +628,12 @@ COPY <replaceable class="parameter">count</replaceable>`
`628`	`628`	`<row>`
`629`	`629`	`<entry><literal>\</literal><replaceable>digits</replaceable></entry>`
`630`	`630`	`<entry>Backslash followed by one to three octal digits specifies`
`631`		`- thecharacter with that numeric code</entry>`
	`631`	`+ thebyte with that numeric code</entry>`
`632`	`632`	`</row>`
`633`	`633`	`<row>`
`634`	`634`	`<entry><literal>\x</literal><replaceable>digits</replaceable></entry>`
`635`	`635`	`<entry>Backslash <literal>x</literal> followed by one or two hex digits specifies`
`636`		`- thecharacter with that numeric code</entry>`
	`636`	`+ thebyte with that numeric code</entry>`
`637`	`637`	`</row>`
`638`	`638`	`</tbody>`
`639`	`639`	`</tgroup>`
`@@ -665,6 +665,12 @@ COPY <replaceable class="parameter">count</replaceable>`
`665`	`665`	`or vice versa).`
`666`	`666`	`</para>`
`667`	`667`
	`668`	`+ <para>`
	`669`	`+ All backslash sequences are interpreted after encoding conversion.`
	`670`	`+ The bytes specified with the octal and hex-digit backslash sequences must`
	`671`	`+ form valid characters in the database encoding.`
	`672`	`+ </para>`
	`673`	`+`
`668`	`674`	`<para>`
`669`	`675`	`<command>COPY TO</command> will terminate each row with a Unix-style`
`670`	`676`	`newline (<quote><literal>\n</literal></quote>). Servers running on Microsoft Windows instead`

Comments

(0)