Re: BUG #5891: Unique index is not unique

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: "Alexander V(dot) Chernikov" <melifaro(at)ipfw(dot)ru>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5891: Unique index is not unique
Date: 2011-03-03 14:39:52
Message-ID: AANLkTik=09UVAcq-TD+dyb+dujeAKJ_oymf-Vjn6fG0F@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 17, 2011 at 4:51 AM, Alexander V. Chernikov
<melifaro(at)ipfw(dot)ru> wrote:
> Identical records:
> meganet=# SELECT count(*), array_agg(bc_payment_id) FROM billing.bc_payments
> GROUP BY contractor_name, payment_date, payment_commission_number,
> payment_sum, contractor_account, contractor_bik, inn HAVING count(*) > 1;
>  count |  array_agg
>
>
> -------+-------------
>
>
>     2 | {6376,6380}
>
>
>     2 | {6947,6605}

Has this database crashed at any point?

Can you reply-all with the output of SELECT ctid, xmin, xmax,
bc_payment_id FROM billing.bc_payments WHERE bc_payment_id IN
(6376,6380,6947,6605)?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-03-03 14:42:38 Re: BUG #5861: lo_import and lo_export methods not working from the client side if database is at remote
Previous Message Robert Haas 2011-03-03 14:33:53 Re: can't build contrib/uuid-ossp