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

From Tom Lane
Subject Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Date
Msg-id 9688.1458605021@sss.pgh.pa.us
Whole thread Raw
In response to Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)  (Marc-Olaf Jaschke <marc-olaf.jaschke@s24.com>)
Responses Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
List pgsql-bugs
Marc-Olaf Jaschke <marc-olaf.jaschke@s24.com> writes:
> PostgreSQL 9.5 ignores rows with the following test case:

I can reproduce this in 9.5 and HEAD on RHEL6, but 9.4 works as expected.
I presume that that points the finger at the abbreviated-keys work.

BTW, what I'm seeing in 9.5/HEAD is that all three comparison senses fail:

u8=# set enable_seqscan TO 0;
SET
u8=#  select * from test where t < 'eai';
 t
---
(0 rows)

u8=#  select * from test where t = 'eai';
 t
---
(0 rows)

u8=#  select * from test where t > 'eai';
 t
---
(0 rows)

            regards, tom lane

pgsql-bugs by date:

Previous
From: Marc-Olaf Jaschke
Date:
Subject: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
Next
From: Robert Haas
Date:
Subject: Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)