| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: clean up obsolete initdb locale handling |
| Date: | 2019-08-12 18:11:55 |
| Message-ID: | 6f738422-ffb2-5e75-1227-8815ee84998f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| v2-0001-initdb-Remove-obsolete-locale-handling.patch | text/plain | 3.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-12 18:17:19 | Re: clean up obsolete initdb locale handling |
| Previous Message | Simon Riggs | 2019-08-12 17:49:31 | Re: Problem with default partition pruning |