| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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 22:40:46 |
| Message-ID: | dcc563d11002031440t33d86ceq33466792672dcd35@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Feb 3, 2010 at 3:31 PM, Wang, Mary Y <mary(dot)y(dot)wang(at)boeing(dot)com> wrote:
> Thanks Scott and Tom.
> Yes. I know, I know that I need to upgrade :-)
> What would be the newer version of pgsql (I mean a bit higher version of my current version) that provides that capability of telling me what the duplicated key was ?
I'd recommend going to 8.3.x if possible, or 8.4.2, the latest version.
Not sure how far back it would tell you which value caused the
failure, but more importantly, 8.3 is will run circles around 7.1 and
is much easier to keep happy from a maintenance perspective.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-02-03 22:42:16 | Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index |
| Previous Message | Wang, Mary Y | 2010-02-03 22:31:42 | Re: PQendcopy:resetting connection Problem and Cannot insert a duplicate key into unique index |