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 dates and corrected the problem with the load. However I noticed that the error message I got indicated the backend died, so I thought I should try to get a simpler case that shows the same problem. Below is a short psql example run against a 7.3 database that also gets the backend to crash, though not in the middle of a large transaction. bruno=> create table test (col1 timestamp); CREATE TABLE bruno=> copy test from stdin; Enter data to be copied followed by a newline. End with a backslash and a period on a line by itself. >> 11/31/02 >> \. ERROR: copy: line 1, Bad timestamp external representation '11/31/02' lost synchronization with server, resetting connection
---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
