Re: BUG #13862: Duplicated rows for a table with primary key

From: "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: y(dot)chaitanya(at)tcs(dot)com, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13862: Duplicated rows for a table with primary key
Date: 2016-01-15 16:34:20
Message-ID: CACACo5QtmR2MUT130Dn8V1x=2NURNgG6Yi0WTav_6ojhpvg3Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 15, 2016 at 5:26 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Fri, Jan 15, 2016 at 1:56 AM, <y(dot)chaitanya(at)tcs(dot)com> wrote:
>
>> HI David,
>>
>> Thanks for your time,
>>
>> For us , the basic primary key feature is violated, So there must be
>> some reason for this, Please let me know if you need any other information
>> for finding the root cause.
>> Also some advice to avoid this will be helpful.
>>
>
> ​I neither have the time nor expertise to play email technical support for
> an issue like this.
>

More specifically, OP please take some time to follow this guide:
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

--
Alex

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-01-15 16:54:11 Re: BUG #13865: PQresultStatus returns PGRES_COPY_OUT instead of PGRES_FATAL_ERROR for certain bad COPY statement
Previous Message David G. Johnston 2016-01-15 16:26:04 Re: BUG #13862: Duplicated rows for a table with primary key