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

From Tom Lane
Subject Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?
Date
Msg-id 25608.1247079073@sss.pgh.pa.us
Whole thread Raw
In response to Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Tom Lane wrote:
>> 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.

> Agreed. In EXEC_BACKEND case, main() sets them to the same system
> defaults before restore_backend_variables() is called.

Right.  It would only matter if the postmaster changed them again later,
but so far as I can see it does not.  The most likely future change that
would make it do so would be establishing GUC variables to control them,
but we still wouldn't need a special mechanism to transmit the settings.

Will go remove those calls.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?
Next
From: Alvaro Herrera
Date:
Subject: Re: tsvector extraction patch