From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Mathieu De Zutter <mathieu(at)dezutter(dot)org> |
Subject: | Re: BUG #4913: Row missing from primary key index |
Date: | 2009-07-09 23:21:53 |
Message-ID: | 20090709232153.GP6414@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Andrew Gierth wrote:
> >>>>> "Mathieu" == "Mathieu De Zutter" <mathieu(at)dezutter(dot)org> writes:
>
> Mathieu> I have a table log_event with a primary key on an integer
> Mathieu> 'id', called log_event_pkey.
>
> Mathieu> The tables contains a duplicate for id = 15723018. The
> Mathieu> duplicate (note that besides the id, all data differs)
> Mathieu> doesn't seem to be known by the index at all.
> [snip]
>
> This was first reported on IRC and I spent a little time working with
> the OP trying to dig up info to suggest a cause; here is the relevent
> data (all provided by the OP at my request). I have not been able to
> suggest a possible cause based on this.
How are the event_timestamps generated? If these come from the
transaction timestamp, it is even more weird that tuples seemingly
inserted by the same xmin have differing timestamps.
FWIW I think I've seen similar cases before.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2009-07-09 23:48:11 | Re: BUG #4913: Row missing from primary key index |
Previous Message | Dan Boeriu | 2009-07-09 23:21:31 | BUG #4914: uuid_generate_v4 not present in either source or yum/rpm |