The documentation says:
"The specified null string is sent by COPY TO without adding any
backslashes; conversely, COPY FROM matches the input against the null
string before removing backslashes."
Those seem inconsistent with the following behavior:
postgres=# copy foo to '/tmp/a.copy' null '\0';
postgres=# copy foo from '/tmp/a.copy' null '\0';
ERROR: invalid byte sequence for encoding "UTF8": 0x00
CONTEXT: COPY foo, line 2: "\0"
$ cat /tmp/a.copy
COPY TO seems to follow the documentation, inserting the null string
without modification into the output file. COPY FROM seems to de-escape
the input before trying to match it against the null string, leading to
the invalid byte sequence.
standard_conforming_strings is on.
pgsql-bugs by date
|Next:||From: kontakt||Date: 2012-03-26 00:00:05|
|Subject: BUG #6556: earthdistance module has lacking documentation|
|Previous:||From: Tom Lane||Date: 2012-03-25 21:06:46|
|Subject: Re: check_locale() and the empty string |