Re: GUC and postgresql.conf docs - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: GUC and postgresql.conf docs
Date
Msg-id Pine.LNX.4.44.0305131002430.1617-100000@peter.localdomain
Whole thread Raw
In response to Re: GUC and postgresql.conf docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: GUC and postgresql.conf docs
List pgsql-hackers
Tom Lane writes:

> > {"server_encoding", PGC_USERSET}, &server_encoding_string,
> >         "SQL_ASCII", assign_server_encoding, show_server_encoding
>
> I'm not sure why this one is marked PGC_USERSET --- seems like it should
> not be possible to override it from SET.  It should be documented as a
> read-only option, I think.  (Looks ... actually it is set up that way
> in CVS tip.)

Do we even need this one?  If you want to find out the server encoding
(which should be rare anyway), you can select it from pg_database.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GUC and postgresql.conf docs
Next
From: "postgresql"
Date:
Subject: can we implement the updatable view through rule system?