Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index
Date: 2010-02-03 15:42:44
Message-ID: 10826.1265211764@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)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 and count 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message john blair 2010-02-03 19:15:16 statically linking libpq to psycopg2
Previous Message Tom Lane 2010-02-03 15:25:39 Re: stat collector is not using