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-03 23:07:31 |
Message-ID: | 23616.1317683251@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>> No, because there are people who do intentionally use placeholder
>> variables as session-local storage, and that would be taking away
>> that capability.
> Or do you want to open SET typo.wrogn TO 'foobar' to just work silently?
Well, right at the moment it *does* work silently, as long as the prefix
is one you listed in custom_variable_classes. I don't think we want to
take that away, and in particular I don't want to assume that every
variable will be declared in advance. It's a fairly safe bet that there
are some apps out there that would be broken by such a requirement.
At the same time, I'd kind of like to see a facility for declaring such
variables, if only so you could define them to be bool/int/real not just
strings. But this is getting far afield from the immediate proposal,
and no I'm not volunteering to do it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2011-10-03 23:10:07 | Re: Bug with pg_ctl -w/wait and config-only directories |
Previous Message | Andrew Dunstan | 2011-10-03 22:59:09 | restoring an object to a different name |