Re: pgsql: Add option to use ICU as global locale provider

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Add option to use ICU as global locale provider
Дата
Msg-id 1069623.1647616024@sss.pgh.pa.us
обсуждение исходный текст
Ответ на pgsql: Add option to use ICU as global locale provider  (Peter Eisentraut <peter@eisentraut.org>)
Ответы Re: pgsql: Add option to use ICU as global locale provider  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-committers
Julien Rouhaud <rjuju123@gmail.com> writes:
> That being said, we could save the result and explicitly close the collator.
> That wouldn't make much difference in initdb (but may be a bit cleaner), but I
> see that there's a similar coding in createdb(), which seems like it could leak
> some memory according to ucol_close man page.

FYI, I verified using valgrind that (as of HEAD) there is a leak
when creating a database with ICU collation that doesn't appear
when creating one with libc collation.  It's not a lot, a few
hundred bytes per iteration, but it's there.

            regards, tom lane



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

Предыдущее
От: Julien Rouhaud
Дата:
Сообщение: Re: pgsql: Add option to use ICU as global locale provider
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Remove workarounds for avoiding [U]INT64_FORMAT in translatable