Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index - Mailing list pgsql-general

From Tom Lane
Subject Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index
Date
Msg-id 10826.1265211764@sss.pgh.pa.us
Whole thread Raw
In response to PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
Responses Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
List pgsql-general
"Wang, Mary Y" <mary.y.wang@boeing.com> writes:
> I managed to restore my database. However, one table is not restored.
> The error message that I was received was "copy: line 3057, Cannot insert a duplicate key into unique index
users_pkey..."and then "...PQendcopy:resetting connection" 

> Then I went to the log file (my debug file was set to level 5),
> ProcessUtility: COPY "users"  FROM stdin;
> ERROR:  copy: line 3057, Cannot insert a duplicate key into unique index users_pkey"

> My question is that line #3057.  Do I count it from the line where it did "COPY "users" FROM stdin" as the first line
andcount up to 3057 lines (that line is the problem)? 

IIRC, even as far back as 7.1, that should be read as "the 3057'th row
of COPY data for this table".  So you can count forward 3057 lines from
the COPY command in the dump file ... unless you have any embedded
newlines in your data, in which case it could get a bit painful to
count correctly.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: stat collector is not using
Next
From: john blair
Date:
Subject: statically linking libpq to psycopg2