Bug in psql's "-R" option?

From: Murthy Kambhampaty <murthy(dot)kambhampaty(at)goeci(dot)com>
To: "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
Subject: Bug in psql's "-R" option?
Date: 2002-11-05 19:07:03
Message-ID: 2D92FEBFD3BE1346A6C397223A8DD3FC09206B@THOR.goeci.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2002-11-05 19:20:55 Re: Bug in psql's "-R" option?
Previous Message Murthy Kambhampaty 2002-11-05 18:50:58 Re: loading and unloading rows