Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?
Date: 2009-07-08 18:51:13
Message-ID: 25608.1247079073@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2009-07-08 19:38:15 Re: tsvector extraction patch
Previous Message Heikki Linnakangas 2009-07-08 18:46:09 Re: Does EXEC_BACKEND mode still need to propagate setlocale settings?