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

From Peter Geoghegan
Subject Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Date
Msg-id CAM3SWZT66kQJak-gD7+-=w=s02tksDSPO6ywXXL9UO1TRs9rpg@mail.gmail.com
Whole thread Raw
In response to Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On Wed, Mar 23, 2016 at 11:56 AM, Robert Haas <robertmhaas@gmail.com> wrote:
> I think that something like the attached would be a reasonable
> approach to the problem.  If we later decide this is altogether
> hopeless, we can do a more thorough job removing the code that can be
> reached when collate_c && abbreviate, but let's not do that right now.

This patch looks good to me.

I think that disabling abbreviation when the C collation is in makes
no sense, though. This has nothing to do with abbreviation as such,
and everything to do with glibc.

--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Next
From: Robert Haas
Date:
Subject: Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)