| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [RFC] Extend namespace of valid guc names |
| Date: | 2013-09-05 21:05:28 |
| Message-ID: | 20130905210528.GA556998@alap2.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-02-26 13:08:54 +0100, Andres Freund wrote:
> Just for reference, thats the grammar for SET/SHOW:
>
> var_name: ColId { $$ = $1; }
> | var_name '.' ColId
>
> Any arguments whether we should try to validate postgres -c,
> set_config and SET/SHOW the same?
Any input here?
Currently set_config() and postgres -c basically don't have any
restrictions on the passed guc name whereas SHOW, SET and
postgresql.conf do.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-09-05 21:06:41 | Re: strange IS NULL behaviour |
| Previous Message | Alvaro Herrera | 2013-09-05 19:53:38 | Re: Re: [HACKERS] Is it necessary to rewrite table while increasing the scale of datatype numeric? |