Does EXEC_BACKEND mode still need to propagate setlocale settings? - Mailing list pgsql-hackers

From Tom Lane
Subject Does EXEC_BACKEND mode still need to propagate setlocale settings?
Date
Msg-id 24885.1247076995@sss.pgh.pa.us
Whole thread Raw
Responses Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?
List pgsql-hackers
The recent bug report about CheckMyDatabase() failing to use
pg_perm_setlocale() led me to look for other uses of setlocale() that
might be wrong.  I found two fishy calls in restore_backend_variables().
I am thinking though that the correct fix is to delete them and get
rid of the overhead of transmitting the postmaster's setlocale settings
to child processes this way.  A regular backend is going to do
CheckMyDatabase momentarily, and in any case it seems to me that the
postmaster hasn't bothered to change these values off the system defaults
and so there is no need to do anything special to inherit its values.

Comments?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: 8.4.0 vs. locales vs. pl/perl?
Next
From: Alvaro Herrera
Date:
Subject: Re: [pgsql-www] commitfest.postgresql.org