From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: bug fix request |
Date: | 2004-11-29 07:21:44 |
Message-ID: | 9661.1101712904@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> I would like to beg for some sort of fix to psql's handling of COPY data
> if the COPY fails.
> Presently you get a million lines of '\N command not recognised' and
> various other random things because if a line of the copy fails due to
> say a FK constraint, or even if the COPY is run in an aborted
> transaction, it tries to execute all the stdin data as actual
> statements.
I'd like to see a test case for this in v3 protocol. It was definitely
a problem before that, but I thought I fixed it.
> Also, sometimes when you copy and paste SQL into a psql window, it
> executes help on commands for each line, although it doesn't affect the
> paste. That is also really annoying.
Disable tab completion, or don't paste tabs. I don't think psql can be
expected to recognize that a tab is coming from pasted input.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-11-29 07:33:14 | Re: bug fix request |
Previous Message | Andrew Dunstan | 2004-11-29 07:17:30 | Re: [HACKERS] Adding Reply-To: <listname> to Lists |