Peter Eisentraut <peter_e@gmx.net> writes:
>> But it hasn't got done yet. (Peter, would it be
>> easy to make GUC handle this? There'd need to be some way to cause
>> guc.c to do a putenv() ...)
> I thought pg_control was the place for this. Any idea how long a locale
> string can legally be? Doesn't look too hard beyond that.
That would work too, I guess.
> Then again, perhaps this should be a per-database thing, much like the
> encoding. The postmaster doesn't do any collating, so it should be safe
> to have different locale in different backends. -- Unless someone puts an
> index on pg_database.datname. :-)
There already is an index on pg_group.groname, so I think we'd better be
conservative and require the same locale across the whole installation.
Hmm ... doesn't that mean that per-database encoding is a bogus concept
too!?
regards, tom lane
