Re: clean up obsolete initdb locale handling - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: clean up obsolete initdb locale handling
Date
Msg-id 6f738422-ffb2-5e75-1227-8815ee84998f@2ndquadrant.com
Whole thread Raw
In response to Re: clean up obsolete initdb locale handling  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: clean up obsolete initdb locale handling  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2019-08-08 17:51, Tom Lane wrote:
> However, I don't much like the choice to set LC_COLLATE and LC_CTYPE
> differently.  That seems to be risking weird behavior, and for what?
> I'd be inclined to just remove the WIN32 stanza, initialize all
> three of these variables with "", and explain it along the lines of
> 
>     * In the postmaster, absorb the environment values for LC_COLLATE
>     * and LC_CTYPE.  Individual backends will change these later to
>     * settings taken from pg_database, but the postmaster cannot do
>     * that.  If we leave these set to "C" then message localization
>     * might not work well in the postmaster.

OK, let's do it like that.  Updated patch attached.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Problem with default partition pruning
Next
From: Tom Lane
Date:
Subject: Re: clean up obsolete initdb locale handling