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

Peter Geoghegan <pg@heroku.com> writes:
> My concern was not merely "academic" (i.e. it was not limited in scope
> to things that don't make B-Tree indexes corrupt). Pretty sure that we
> need to start thinking of this as a problem with strcoll() that
> strxfrm() does not have for more fundamental reasons, because
> strcoll() says that the first string in the de_DE sorted list is
> *greater* than the third string.

[ squint... ]  I was looking specifically for that sort of misbehavior
in my test program, and I haven't seen it.

            regards, tom lane