| 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:27:13 |
| Message-ID: | CAM3SWZTfjsRpnW+xK1w2YprooLTsLecCuR8omKRpVk1CWwvHkw@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.
Conferred with Robert. This is my first suspicion. More in a little while.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-22 00:34:17 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Robert Haas | 2016-03-22 00:26:25 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-03-22 00:34:17 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Robert Haas | 2016-03-22 00:26:25 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |