| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GUC and postgresql.conf docs |
| Date: | 2003-05-13 08:04:03 |
| Message-ID: | Pine.LNX.4.44.0305131002430.1617-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | postgresql | 2003-05-13 09:01:42 | can we implement the updatable view through rule system? |
| Previous Message | Tom Lane | 2003-05-13 05:25:05 | Re: GUC and postgresql.conf docs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2003-05-13 09:08:40 | Re: SQL99 CREATE TABLE ... (LIKE parent_table) |
| Previous Message | Tom Lane | 2003-05-13 05:25:05 | Re: GUC and postgresql.conf docs |