Robert Haas <robertmhaas@gmail.com> writes:
>> I was a little worried that it was too much to hope for that all libc
>> vendors on earth would ship a strxfrm() implementation that was actually
>> consistent with strcoll(), and here we are.
BTW, the glibc discussion starting here:
https://sourceware.org/ml/libc-alpha/2015-09/msg00196.html
should put substantial fear in us about the advisability of putting strxfrm
results on-disk, as I understand we're now doing in btrees.
I was led to that while looking to see if there were any already-filed
glibc bug reports concerning this issue. AFAICS there are not, which
is odd if the bug is gone in more recent releases ...
regards, tom lane
