Re: pgsql: Add option to use ICU as global locale provider - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Add option to use ICU as global locale provider
Date
Msg-id 1069623.1647616024@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Add option to use ICU as global locale provider  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: pgsql: Add option to use ICU as global locale provider
List 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 by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: pgsql: Add option to use ICU as global locale provider
Next
From: Tom Lane
Date:
Subject: pgsql: Remove workarounds for avoiding [U]INT64_FORMAT in translatable