| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Drew Wilson <amw(at)speakeasy(dot)net>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: initdb "Fails to initialize lc_time" (using 7.3.1) |
| Date: | 2002-08-09 22:54:25 |
| Message-ID: | Pine.LNX.4.44.0208092150080.927-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Tom Lane writes:
> Even if that means you fail to detect that locale B is broken in some
> way?
We don't pretend to do a thorough check of the locales anyway. We'd have
to run a full test suite to do that. Of course, it would be nice to check
whether setlocale() works, but initdb should do that itself then.
> I'm not at all sure I buy this reasoning. If the user has told us a
> locale to use on the initdb command line, seems to me he wants us to use
> that locale, period.
Think about it this way: If I'm the admin and a customer tells me to
install a database for him in Greek, which localization would I want for
responses from initdb?
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-08-09 22:55:37 | Re: initdb "Fails to initialize lc_time" (using 7.3.1) |
| Previous Message | Jie Liang | 2002-08-09 18:27:55 | Re: problem with select into and timestamp. |