Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Marc-Olaf Jaschke <marc-olaf(dot)jaschke(at)s24(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Date: 2016-03-23 01:02:15
Message-ID: 24020.1458694935@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Mar 22, 2016 at 8:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So much for the theory that it's fixed in RHEL7. I now think that the
>> glibc folk actually do not know about this, and have accordingly filed
>> https://bugzilla.redhat.com/show_bug.cgi?id=1320356

> Good plan, but what do we do between now and when they fix it? This
> seems quite bad.

At the moment I think we're still in information-gathering mode.
The upstream reaction to this will be valuable data. In the meantime,
I'd still like to find out which other platforms have similar issues.
I really kinda doubt the upthread report that Ubuntu doesn't have a
comparable problem, for instance, given the lack of any evidence that
this is a known/fixed issue in glibc.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephen Frost 2016-03-23 01:15:09 Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Previous Message Robert Haas 2016-03-23 00:57:05 Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2016-03-23 01:15:09 Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Previous Message Álvaro Hernández Tortosa 2016-03-23 01:00:34 Re: about google summer of code 2016