Re: BUG #5891: Unique index is not unique - Mailing list pgsql-bugs

From Robert Haas
Subject Re: BUG #5891: Unique index is not unique
Date
Msg-id AANLkTik=09UVAcq-TD+dyb+dujeAKJ_oymf-Vjn6fG0F@mail.gmail.com
Whole thread Raw
In response to BUG #5891: Unique index is not unique  ("Alexander V. Chernikov" <melifaro@ipfw.ru>)
List pgsql-bugs
On Thu, Feb 17, 2011 at 4:51 AM, Alexander V. Chernikov
<melifaro@ipfw.ru> wrote:
> Identical records:
> meganet=3D# SELECT count(*), array_agg(bc_payment_id) FROM billing.bc_pay=
ments
> GROUP BY contractor_name, payment_date, payment_commission_number,
> payment_sum, contractor_account, contractor_bik, inn HAVING count(*) > 1;
> =A0count | =A0array_agg
>
>
> -------+-------------
>
>
> =A0 =A0 2 | {6376,6380}
>
>
> =A0 =A0 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)?

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

pgsql-bugs by date:

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