| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should we get rid of custom_variable_classes altogether? |
| Date: | 2011-10-04 14:42:39 |
| Message-ID: | 7997.1317739359@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> What I have in mind for extensions now that c_v_c is out would be to be
> able to declare any GUC in the control file, with default values, and
> without forcing extension to handle the GUC in its .so I don't think
> we have to change the code beside removing the c_v_c checks here.
What's the point of that? A value in an extension control file isn't
particularly easily accessible. You'd basically only see it when
loading the extension, and that's a scenario in which the existing
mechanism works just fine. I see no reason to break existing code
here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-10-04 14:55:05 | Re: Bug with pg_ctl -w/wait and config-only directories |
| Previous Message | Greg Stark | 2011-10-04 14:28:37 | Re: Bug with pg_ctl -w/wait and config-only directories |