Peter Eisentraut wrote:
On Thursday 02 April 2009 21:38:06 Tom Lane wrote:
Heikki Linnakangas <heikki.linnakan...@enterprisedb.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.
Those are good points, but note that createdb already *has* a --locale option
that does something specific, so in light of your earlier argument that
createdb and CREATE DATABASE options should be the same, the possibilities for
a future CREATE DATABASE ... LOCALE=foo are already being constrained.
Hmm, maybe we should remove the --locale option from createdb as well,
until we can implement it in a way that will set all the lc_* settings.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
