| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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 04:04:18 |
| Message-ID: | CAM3SWZQnF3AfMwJHVdjmfmy9T2D2esX04aTfwZo2kNvwUp8OEQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Mar 21, 2016 at 7:54 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> FWIW, I do not think you can dismiss it as "not our bug" if a large
> fraction of existing glibc installations share the issue. It might
> be a glibc bug, but we'll have to find a workaround.
I didn't say that. I strongly agree.
>> Maybe we can write a test-case that lets check_strxfrm_bug() detect
>> this issue, which would be ideal. But, again, I need to see what's
>> going on with strxfrm() on affected systems before I can do anything.
>
> Happy to test if you can provide a test case.
Can you look at generating a textual representation of the strxfrm()
blobs in question, using Robert's tool?:
That would give me some basis for writing a test.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-22 04:10:52 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| Previous Message | Tom Lane | 2016-03-22 02:54:17 | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-03-22 04:07:10 | Re: Relax requirement for INTO with SELECT in pl/pgsql |
| Previous Message | Peter Geoghegan | 2016-03-22 04:02:19 | Re: Minor bug affecting ON CONFLICT lock wait log messages |