| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | sergey(dot)frolov(at)smetarik(dot)ru |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14940: Duplicated records inspite of primary key and unique constraint |
| Date: | 2017-12-01 17:15:13 |
| Message-ID: | 20171201171513.if4pd67kh5sl7u53@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
sergey(dot)frolov(at)smetarik(dot)ru wrote:
> select ctid,xmin,xmax, id, base_id, norm_id from nb.nb_basedtl where id =
> 11658502 ;-- expected ONE row
>
> (0,49);364507;0;11658502;269;46203
> (0,49);370881;0;11658502;269;46203
> (0,49);370882;0;11658502;269;46203
Since these rows all have the same CTID, it looks like the index on id
must be corrupt and returned the same tuple more than once. But the
weird thing is that the xmin differs ... How can that be? Does this
change if you set enable_indexscan and enable_bitmapscan to off?
Would you try running amcheck on this index?
https://github.com/petergeoghegan/amcheck
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2017-12-01 17:15:47 | Re: BUG #14941: Vacuum crashes |
| Previous Message | Tomas Vondra | 2017-12-01 17:07:08 | Re: BUG #14940: Duplicated records inspite of primary key and unique constraint |