| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Subject: | Re: 8.4 open items list |
| Date: | 2009-04-02 18:38:06 |
| Message-ID: | 13884.1238697486@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:
> Now, what about the idea of providing a shorthand LOCALE='foo',
> mirroring --locale=foo initdb option? It seems like a good idea, because
> you almost never want to set LC_COLLATE and LC_CTYPE differently. If we
> do that, should LOCALE=foo also imply a per-database lc_messages,
> lc_monetary, lc_numeric and lc_time settings? It seems like it should
> for the sake of consistency.
The comment upthread was that we can/should leave that for 8.5.
I agree with that at this point. I think the above proposal is
not as straightforward as it looks (in particular per-DB lc_messages
has unpleasant implications for the postmaster log) and we should
not tackle it in a hasty manner.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-02 18:50:57 | Re: [HACKERS] string_to_array with empty input |
| Previous Message | Jeff Davis | 2009-04-02 18:37:33 | Re: [HACKERS] Mentors needed urgently for SoC & PostgreSQL Student Internships |