From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | curd(dot)reinert(at)ppi(dot)de |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #8382: Duplicate primary key |
Date: | 2013-08-13 17:50:35 |
Message-ID: | CAM-w4HP6Xm=QgLaTGE6o0HNY1-fGgByEYf43Nf4=OyE+uETiKw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Aug 13, 2013 at 2:50 PM, <curd(dot)reinert(at)ppi(dot)de> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8382
> Logged by: Curd Reinert
> Email address: curd(dot)reinert(at)ppi(dot)de
> PostgreSQL version: 9.0.5
The current bug-fix release for Postgres 9 is 9.0.13. There was an
extremely high profile security vulnerability fixed in 9.0.13 so I
would strongly recommend updating.
I see bugs that could cause this in both 9.0.7 and 9.0.11. However
both are very rare and hard to believe you would see either of them
happen repeatedly. Unless you're calling CREATE INDEX CONCURRENTLY
*often* on this system?
Do you know anything about the history of how often the system was
rebooted -- either the host or the virtual machine? Also, have you run
a memory checker on the system?
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Curd Reinert | 2013-08-14 08:28:16 | Re: BUG #8382: Duplicate primary key |
Previous Message | curd.reinert | 2013-08-13 13:50:01 | BUG #8382: Duplicate primary key |