Re: Server locale?

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, Postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Server locale?
Date: 2002-10-10 10:28:58
Message-ID: 20021010102858.GC25467@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Oct 08, 2002 at 10:02:43PM -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> writes:
> > > I good know why PostgreSQL not use all locale, I talked about SHOW
> > > command. Why this command not show all LC_ values?
> >
> > The GUC code doesn't currently have a concept of "a variable it's not
> > allowed to change, ever". If it did, we could expose initdb-time values
> > like LC_COLLATE that way. Might be a good thing to do, down the road
> > --- we could replace most of the uses of pg_controldata with read-only
> > SHOW variables.
>
> Added to TODO:
>
> o Allow SHOW of non-modifiable variables, like pg_controldata

Ok, I'm looking at guc.c right now and is there any reason why you couldn't
just add a PGC_READONLY that throws an error when you try to change it. If
this is the case I'd be willing to give it a shot.

Or did you have something more substantial in mind?

--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Savita 2002-10-10 11:06:54 Problem running postgre as a windows NT service
Previous Message Richard Huxton 2002-10-10 09:26:12 Re: access time performance problem