| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Marc-Olaf Jaschke <marc-olaf(dot)jaschke(at)s24(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Date: | 2016-03-23 18:14:35 |
| Message-ID: | CAM3SWZRYSOkSeog_68B9mMac=PBJkH4dW2aee57kA0W-sFw06w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Mar 23, 2016 at 11:09 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> We want to get it back to working. But short-term, it's more important to
> limit the scope of the brokenness, since this is a version that people are
> putting in production. Once we have enough info to safely say we've put a
> workaround in place, we turn it back on.
Do you think it's possible that my amcheck tool might have a role to
play here? I wrote it for exactly this kind of scenario. If we could
get it reviewed, then a pre-release version compatible with 9.5 could
be made available. I'd be willing to work on that side of things if
core are receptive. Early prototypes of the tool were used to detect
collation incompatibility issues in production.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-23 18:32:26 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Tom Lane | 2016-03-23 18:13:56 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Sitnikov | 2016-03-23 18:15:32 | Re: NOT EXIST for PREPARE |
| Previous Message | Alvaro Herrera | 2016-03-23 18:13:59 | Re: Rationalizing code-sharing among src/bin/ directories |