Re: Should we get rid of custom_variable_classes altogether?
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: David Fetter <david@fetter.org>, Andrew Dunstan <andrew@dunslane.net>, Magnus Hagander <magnus@hagander.net>, pgsql-hackers@postgresql.org
Date: 2011-10-03T20:40:25Z
Lists: pgsql-hackers
Dimitri Fontaine <dimitri@2ndQuadrant.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. regards, tom lane