Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5)
От | Tom Lane |
---|---|
Тема | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
Дата | |
Msg-id | 20828.1458690675@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Missing rows with index scan when collation is not "C"
(PostgreSQL 9.5)
Re: Missing rows with index scan when collation is not "C" (PostgreSQL 9.5) |
Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: