Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Date
Msg-id CAM3SWZTn2a7w5gyM0JawZBok6wDtn9k5shFSZx7ZbGTn0k=ibg@mail.gmail.com
Whole thread Raw
In response to Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)  (Peter Geoghegan <pg@heroku.com>)
List pgsql-bugs
On Mon, Mar 21, 2016 at 10:16 PM, Peter Geoghegan <pg@heroku.com> wrote:
> "eai" ->  100c14 01 090909 01 090909 (11 bytes)
> "e a=C3=AD" -> 100c14 01 0b0909 01 090909010235 (14 bytes)

> "eai" ->  100c14 01 080808 01 020202 (11 bytes)
> "e a=C3=AD" -> 100c14 01 080809 01 020202010235 (14 bytes)

Sorry, I have that backwards. The latter output is Tom's de_DE.UTF-8
testcase, showing broken glibc behavior.

--=20
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Next
From: Reece Pegues
Date:
Subject: Re: BUG #14038: substring cuts unicode char in half, allowing to save broken utf8 into table