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 8648.1265236936@sss.pgh.pa.us
Whole thread Raw
In response to 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:
> What would be the newer version of pgsql (I mean a bit higher version of my current version) that provides that
capabilityof telling me what the duplicated key was ? 

Hmm ... [ experiments... ]  For the specific case of COPY into a table
with a pre-existing unique index, it looks like only CVS HEAD will give
you an error message with the exact index value.  However, everything
back to 7.4 will include the text of the whole current line of COPY
data, which probably would be enough to figure out the problem.

            regards, tom lane

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index
Next
From: Walter Coole
Date:
Subject: Re: Why lots of temp schemas are being created