From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | "Kumar, Pawan (Nokia - IN/Bangalore)" <pawan(dot)kumar(at)nokia(dot)com> |
Cc: | "andres(at)2ndquadrant(dot)com" <andres(at)2ndquadrant(dot)com>, "andrew(at)dunslane(dot)net" <andrew(at)dunslane(dot)net>, "josh(at)agliodbs(dot)com" <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: duplicate key entries for primary key -- need urgent help |
Date: | 2019-07-04 18:39:17 |
Message-ID: | 20190704183917.emwzqusy7gbjduqs@development |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 04, 2019 at 06:28:03PM +0000, Kumar, Pawan (Nokia - IN/Bangalore) wrote:
>Thanks for reply.
>
>This has happened very often and at different production system.
>There is no version change. System running with same version since 1 year but duplicate key issue came quiet a time.
>And impact is big because of that and only way to fix is to delete the duplicate primary key.
>Any suggestions to check which logs? Any command to run to get more info during the issue?
>
>Any potential configuration to check?
>Plz suggest
>
Well, I've already pointed out you're missing 2 years worth of fixes, so
upgrading to current minor version is the first thing I'd do. (I doubt
people will be rushing to help you in their free time when you're
missing two years of fixes, possibly causing this issue.)
If the issue happens even after upgrading, we'll need to see more details
about an actual case - commands creating/modifying the duplicate rows,
or anything you can find. It's impossible to help you when we only know
there are duplicate values in a PK.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-07-04 18:44:33 | Re: Periods |
Previous Message | Alvaro Herrera | 2019-07-04 18:33:58 | Re: range_agg |