| 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>, Noah Misch <noah(at)leadboat(dot)com>, Marc-Olaf Jaschke <marc-olaf(dot)jaschke(at)s24(dot)com>, Postgres-Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Date: | 2016-03-23 18:02:32 |
| Message-ID: | CAM3SWZQu-w7A9kW64L4VWHdf_M7fbjGUHumoZY6ztaQ-QAYZ9w@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:23 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I guess that's not terribly surprising. If the glibc maintainers
> haven't managed to get this right for UTF-8 locales, I can't imagine
> why they would have been more careful for non-UTF-8 locales that - I
> would guess - get less use.
We don't want to suggest that locales are broken as such. My inability
to reproduce the original complaint on alternative German locales
(e.g. Austrian) suggest to me that it just "accidentally fails to
fail" for whatever reason (maybe they fail in other ways). I should
say "accidentally fails to not fail", because this is a failure of
strxfrm() to be bug-compatible with strcoll(), which I think needs to
not be forgotten.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-03-23 18:04:44 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Peter Geoghegan | 2016-03-23 18:00:07 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2016-03-23 18:04:44 | Re: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Merlin Moncure | 2016-03-23 18:01:25 | Re: NOT EXIST for PREPARE |