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>, 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-22 00:44:41 |
Message-ID: | CAM3SWZT04ZOVdh5j6kA4hX3kg3XLir28jsvrqT2Cxhv1QDy9kQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Mon, Mar 21, 2016 at 5:26 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> If that is the case, I'd argue that's a glibc problem, not our
> problem. Of course, we could provide an option to disable abbreviated
> keys for the benefit of people who need to work around buggy libc
> implementations.
That would be an easy patch to write. We'd simply have a test within
bttextsortsupport() that had systems that disabled abbreviated keys
for text PG_RETURN_VOID(). Actually, to be more precise we'd put that
next to the Windows code within varstr_sortsupport() (the function is
called btsortsupport_worker in 9.5). It would look at a GUC, I
suppose.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Reece Pegues | 2016-03-22 00:47:23 | Re: BUG #14038: substring cuts unicode char in half, allowing to save broken utf8 into table |
Previous Message | Peter Geoghegan | 2016-03-22 00:34:17 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-03-22 00:59:34 | Re: Request - repeat value of \pset title during \watch interations |
Previous Message | Stas Kelvich | 2016-03-22 00:41:58 | Re: [PATCH] we have added support for box type in SP-GiST index |