Re: How to make results of “localedef” survive “dpkg-reconfigure locales”?

[Thorsten Schöning]

Guten Tag Thorsten Schöning,
am Dienstag, 26. Februar 2019 um 08:28 schrieben Sie:

> BUT Postgres simply still doesn't work, that only works if I use
> "localedef" to create the new locale as an individual archive. And
> that's why it's problematic if that directory gets deleted without
> properly recreation.

> Might this be some Postgres-specific handling of locales for some
> reason? I'm gonna to ask them if they behave specially.

I finally found the reason: I simply never restarted Postgres. :-/

When the directories created for my new locale using "localedef" are
deleted or added, Postgres seems to recognize that instantly whenever
created a connection to some database using that locale. While without
individual directories and the new locale added to the archive only,
which is the default of "dpkg-reconfigure locales", it seems Postgres
simply needs to be restarted once. Afterwards it works as expected.
Without the restart, it doesn't recognize the new contents of the
archive, I guess because it's only opened once per process creation.

Thanks for your help, "Tom H"!

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail: Thorsten.Schoening at AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow