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

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, 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>
Subject: Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Date: 2016-03-23 19:01:36
Message-ID: CAM3SWZT66kQJak-gD7+-=w=s02tksDSPO6ywXXL9UO1TRs9rpg@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:56 AM, Robert Haas <robertmhaas(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2016-03-23 19:04:37 Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Previous Message Robert Haas 2016-03-23 18:56:53 Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-03-23 19:01:44 Re: Relation extension scalability
Previous Message Robert Haas 2016-03-23 18:56:53 Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)