From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Patrik Kudo <kudo@partitur.se>
Cc: pgsql-sql@postgresql.org
Cc: girgen@partitur.se
Subject: Re: Index problem
Date: Wed, 15 Nov 2000 22:54:38 -0500
Message-ID: <18695.974346878@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.21.0011152328500.779-100000@peter.localdomain>
References: <Pine.LNX.4.21.0011152328500.779-100000@peter.localdomain>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, kudo@partitur.se, girgen@partitur.se
Subject: Re: Index problem
In-Reply-To: <18695.974346878@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox