| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, georg(dot)kahest(at)internet(dot)ee, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14112: sorting v and w is broken with et_EE locate |
| Date: | 2016-04-28 04:43:59 |
| Message-ID: | CAM3SWZSxho6XhDX-+1SeDFv6xh_8VVzd6scFk6F-N+ehDdMCcQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Apr 27, 2016 at 9:40 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Geoghegan <pg(at)heroku(dot)com> writes:
>> I ask because I suspect that this might be the same strcoll() bug I
>> describe here: https://bugzilla.redhat.com/show_bug.cgi?id=1320356
>
> The report is against 9.4, though, so strcoll shouldn't matter.
It shouldn't matter that it doesn't agree with strxfrm(), which is the
most important thing, but not the only thing. I think that it would be
interesting to know if this is a strcoll() problem. I have no
intention of pursuing a "fix" from the glibc people.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2016-04-28 05:09:22 | Re: BUG #14112: sorting v and w is broken with et_EE locate |
| Previous Message | Thomas Munro | 2016-04-28 04:43:42 | Re: BUG #14112: sorting v and w is broken with et_EE locate |