Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)

Thanks for the quick bug fix!

I've seen that a wiki page on the subject has been created. Maybe it is =
useful to explicitly mention, that 9.5.1 performance can be partly =
maintained, by changing the collation of text columns to "C", when there =
is no need for special collation handling.

Best regards,
Marc-Olaf Jaschke


> Am 23.03.2016 um 21:07 schrieb Robert Haas <robertmhaas@gmail.com>:
>=20
> On Wed, Mar 23, 2016 at 3:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Robert Haas <robertmhaas@gmail.com> writes:
>>> +#ifndef TRUST_STRXFRM
>>> +     if (!collate_c)
>>> +             abbreviate =3D false;
>>> +#endif
>>=20
>> Ah, I did not realize that abbreviation would be of any value in C =
locale.
>> If it is, then +1 for something like the above.
>=20
> It's actually more likely to help for a C locale than for a non-C =
locale.
>=20
> I have committed this and back-patched it to 9.5.
>=20
> --=20
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company