Re: Duplicate key existant/index visibility bug in 9.3.3

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Erik Jones <ejones(at)engineyard(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:31:47
Message-ID: CAM3SWZQA1B9NKp1g89+Ls=FQPeOw_5yHATQ59o7y9WpQsCZfYw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Erik Jones 2015-01-26 22:35:47 Re: Duplicate key existant/index visibility bug in 9.3.3
Previous Message Tom Lane 2015-01-26 22:19:23 Re: Duplicate key existant/index visibility bug in 9.3.3