Petr Jelinek <[EMAIL PROTECTED]> writes: > (it's same as loris, I posted it just as evidence that --no-locale fixes > all failures)
Advertising
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
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
