Petr Jelinek <pjmodos@seznam.cz> writes:
> (it's same as loris, I posted it just as evidence that --no-locale fixes
> all failures)
I think --no-locale is masking a problem with the recently-installed
UTF16-based comparison code. See my response to Andrew just now.
regards, tom lane