pgsql: Be a bit more rigorous about how we cache strcoll and strxfrm re

Поиск
Список
Период
Сортировка
От Robert Haas
Тема pgsql: Be a bit more rigorous about how we cache strcoll and strxfrm re
Дата
Msg-id E1ZoXAJ-0006V2-Ks@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Be a bit more rigorous about how we cache strcoll and strxfrm results.

Commit 0e57b4d8bd9674adaf5747421b3255b85e385534 contained some clever
logic that attempted to make sure that we couldn't get confused about
whether the last thing we cached was a strcoll() result or a strxfrm()
result, but it wasn't quite clever enough, because we can perform
further abbreviations after having already performed some comparisons.
Introduce an explicit flag in the hopes of making this watertight.

Peter Geoghegan, reviewed by me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/5be94a9eb15a03d8dbc4a5b52760c8776eb3525e

Modified Files
--------------
src/backend/utils/adt/varlena.c |   29 +++++++++++++++++++++--------
1 file changed, 21 insertions(+), 8 deletions(-)


В списке pgsql-committers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: pgsql: Remove obsolete comment.
Следующее
От: Robert Haas
Дата:
Сообщение: pgsql: Put back ssl_renegotiation_limit parameter, but only allow 0.