| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, 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-03 20:47:34 |
| Message-ID: | m2hb3p4xax.fsf@2ndQuadrant.fr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
>> Another compromise might be to allow for defining variable in any class
>> from the configuration files but restrict that to existing classes from
>> the SET command. Wait, that's exactly what happens as soon as there's
>> no explicit custom_variable_classes, right?
>
> No, because there are people who do intentionally use placeholder
> variables as session-local storage, and that would be taking away
> that capability.
They would have to set the variable to its default value in some
configuration file and reload, just as now. They wouldn't have to also
edit custom_variable_classes, that's about it.
Or do you want to open SET typo.wrogn TO 'foobar' to just work silently?
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-10-03 21:12:45 | Re: Bug with pg_ctl -w/wait and config-only directories |
| Previous Message | Peter Eisentraut | 2011-10-03 20:41:29 | Re: Bug with pg_ctl -w/wait and config-only directories |