From: | Erik Jones <ejones(at)engineyard(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Duplicate key existant/index visibility bug in 9.3.3 |
Date: | 2015-01-26 22:54:59 |
Message-ID: | 9ED28E1E-9F4D-4794-A1DD-0D49D085A6E6@engineyard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Jan 26, 2015, at 2:43 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Peter Geoghegan <pg(at)heroku(dot)com> writes:
>> On Mon, Jan 26, 2015 at 2:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> You should definitely also update to 9.3.5 (or next week, 9.3.6) ASAP.
>>> Even if this specific problem isn't fixed, there's a bunch of things
>>> that *are* fixed and will eventually bite you. 9.3.X has not been
>>> one of our most stable release branches :-(
>
>> I didn't consider the bug report in detail, but I think it's likely
>> that this was in fact the bug fixed by
>> 6bfa88acd3df830a5f7e8677c13512b1b50ae813.
>
> Maybe. That would require at least one crash recovery to have happened on
> the server, which Erik seemed to be claiming had not happened. But
> if there were any crashes then it would possibly fit.
Definitely nothing recent crash/recovery-wise but digging further back in the logs it looks like there was a crash recovery run startup back on 2014-09-30, which was about a week after this server was created. I suppose it’s possible that the index has been corrupt since then but only now showing something visible?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-01-26 23:04:31 | Re: Duplicate key existant/index visibility bug in 9.3.3 |
Previous Message | Tom Lane | 2015-01-26 22:43:27 | Re: Duplicate key existant/index visibility bug in 9.3.3 |