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

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 17:58:41
Message-ID: CAM3SWZSUwaPZ3fVTQaugDWucs4MJHBcYYWD726tiiQrwHaVE0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Mar 23, 2016 at 10:56 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> Are you talking about configurable at./configure time, or guc?

I meant a GUC. I think a ./configure option is overkill.

What about the existing caller of strxfrm(), convert_string_datum()?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2016-03-23 18:00:07 Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Previous Message Magnus Hagander 2016-03-23 17:56:32 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 Peter Geoghegan 2016-03-23 18:00:07 Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Previous Message Magnus Hagander 2016-03-23 17:56:32 Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)