Garrett Dangerfield <[EMAIL PROTECTED]> writes:
> I am trying to load a data file into a table using the copy command.
> When I do it on a small subset of the data (gotten using the Linux head command) it
> all works fine, but when I run it on the full dataset, I get the following error:
> ERROR:
Not sure if this is a bug or not, but it seems like one.
I am trying to load a data file into a table using the copy command.
When I do it on a small subset of the data (gotten using the Linux head command) it
all works fine, but when I run it on the full dataset, I get the following error:
ERRO
Bruno Wolff III <[EMAIL PROTECTED]> 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 h
On Wed, Dec 18, 2002 at 09:14:18 -0600,
Bruno Wolff III <[EMAIL PROTECTED]> wrote:
> It looks like when a bad date is entered using COPY the backend connection
> gets killed.
I just tried it with 7.3.1 and get the same error.
---(end of broadcast)
It looks like when a bad date is entered using COPY the backend connection
gets killed.
I noticed this when having a problem loading a database with several copies
in one transaction. The backend died consistantly at the same point, but
not near where the bad dates were. I eventually found the bad
