Re: COPY problem with bad dates

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: COPY problem with bad dates
Date: 2002-12-18 16:30:14
Message-ID: 28298.1040229014@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruno Wolff III <bruno(at)wolff(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2002-12-18 16:42:14 Re: strange problem
Previous Message Bruno Wolff III 2002-12-18 15:45:34 Re: COPY problem with bad dates