Re: COPY problem with bad dates - Mailing list pgsql-bugs

From Tom Lane
Subject Re: COPY problem with bad dates
Date
Msg-id 28298.1040229014@sss.pgh.pa.us
Whole thread Raw
In response to COPY problem with bad dates  (Bruno Wolff III <bruno@wolff.to>)
List pgsql-bugs
Bruno Wolff III <bruno@wolff.to> writes:
> ERROR:  copy: line 1, Bad timestamp external representation '11/31/02'
> lost synchronization with server, resetting connection

This is not a backend crash, this is libpq's standard operating
procedure for recovering from an error during COPY.

If we had a less brain-dead COPY protocol (ie, one that actually had
provisions for error abort), we'd not have to do this.  See plans for
7.4 protocol revisions ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: COPY problem with bad dates
Next
From: Tom Lane
Date:
Subject: Re: strange problem