Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Date
Msg-id CA+TgmoaRTWGYYXP-LhOv91DyS5xrjR55uo9wNG7FiNjqP1j+sQ@mail.gmail.com
Whole thread Raw
In response to Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)  (Peter Geoghegan <pg@heroku.com>)
List pgsql-bugs
On Thu, Mar 24, 2016 at 9:04 AM, Magnus Hagander <magnus@hagander.net> wrote:
> Even if we can't sneak amcheck into 9.5, if we can show that it detects the
> problem, then just being able to direct people to "get amcheck from 9.6 if
> you want to check if the reindex is necessary" would still be a strong
> improvement over nothing.

I agree that back-patching amcheck into 9.5 would be unprecedented,
but it wouldn't be crazy: shipping an extra contrib module with no
additional dependencies shouldn't break anything for existing users.

However, the fact that the patch is not "Ready for Committer" at this
point means that it is not going to be available in time for next
week's maintenance releases, or very possibly, for 9.6.  Time grows
very short.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14042: bug, PostgreSQL not cleanup temp table info after crash.
Next
From: Bernd Helmle
Date:
Subject: Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)