Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAG3u7s39605
	for <pgsql-sql@postgresql.org>; Wed, 15 Nov 2000 22:56:07 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eAG3scD18698;
	Wed, 15 Nov 2000 22:54:38 -0500 (EST)
To: Peter Eisentraut <peter_e@gmx.net>
cc: Patrik Kudo <kudo@partitur.se>, pgsql-sql@postgresql.org,
	girgen@partitur.se
Subject: Re: Index problem 
In-reply-to: <Pine.LNX.4.21.0011152328500.779-100000@peter.localdomain> 
References: <Pine.LNX.4.21.0011152328500.779-100000@peter.localdomain>
Comments: In-reply-to Peter Eisentraut <peter_e@gmx.net>
	message dated "Wed, 15 Nov 2000 23:33:18 +0100"
Date: Wed, 15 Nov 2000 22:54:38 -0500
Message-ID: <18695.974346878@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200011/125
X-Sequence-Number: 156

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