Bug in psql's "-R" option? - Mailing list pgsql-admin

From Murthy Kambhampaty
Subject Bug in psql's "-R" option?
Date
Msg-id 2D92FEBFD3BE1346A6C397223A8DD3FC09206B@THOR.goeci.com
Whole thread Raw
Responses Re: Bug in psql's "-R" option?
List pgsql-admin
There seems to be a bug in psql's -R option (and the -P recordsep= )
version. I find that whereas the following succeeds:

/usr/local/pgsql/bin/psql -U xxxx -d xxxx -h xxxx \
    -P format=unaligned -P fieldsep='\t' -P tuples_only \
    -c "select * from tab where yoo='hoo'" | /usr/local/pgsql/bin/psql
-U xxxx -d xxxx -h xxxx \
    -c "copy bar from stdin"

adding -R '\n' or -P recordsep='\n' or -P recordsep=newline all give an
error that the last field's data is too long for that field's format.
Presently, this seems a bogus option, since the COPY command cannot handle
any record separator except a newline, but the documentation for the "copy
from" command states that '\n' will be parsed as a newline, so this seems a
bug.

pgsql-admin by date:

Previous
From: Murthy Kambhampaty
Date:
Subject: Re: loading and unloading rows
Next
From: Bruce Momjian
Date:
Subject: Re: Bug in psql's "-R" option?