Re: PostgreSQL 12 installation fails because locale name contained non-english characters
От | Tom Lane |
---|---|
Тема | Re: PostgreSQL 12 installation fails because locale name contained non-english characters |
Дата | |
Msg-id | 11659.1572974541@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: PostgreSQL 12 installation fails because locale name containednon-english characters (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: PostgreSQL 12 installation fails because locale name contained non-english characters
|
Список | pgsql-bugs |
Bruce Momjian <bruce@momjian.us> writes: > On Thu, Oct 24, 2019 at 11:06:01AM +0000, Skjalg A. Skagen wrote: >> I tried to install PostgreSQL 12 with the "Norwegian Bokmål, Norway" locale in >> hope that it would, among other things, provide proper support for Norwegian >> characters out-of-the-box. >> But initcluster.vbs appear to fail during post-install because the locale name >> contains a Norwegian character that is being mishandled (full log in attached >> zip file): >> initdb: error: invalid locale name "NorwegianBokm†l,Norway" > This has been fixed with the this patch: > https://www.postgresql.org/message-id/E1iMcHC-0007Ci-7G@gemulon.postgresql.org Hm, I'm not entirely sure that it has been. The original code supposed that the locale name is spelled "Norwegian (Bokmål)_Norway", and the recent patch you mention extended that to allow "Norwegian Bokmål_Norway". But this report, if accurate, shows yet another variant. Skjalg, would you confirm that there's a comma and space before "Norway" in the locale name as you see it? (Your log clearly shows it with a space in the registry entries, but it looks like initdb might be seeing it as not having any spaces, which is why I'm confused.) I wonder whether we need to relax the matching code to be entirely agnostic about spaces and punctuation in the Windows locale name. regards, tom lane
В списке pgsql-bugs по дате отправления: