Re: Per-function GUC settings: trickier than it looked

"Florian G. Pflug" <fgp@phlo.org> writes:
> At least for me, the least surprising behaviour would be to
> revert it too. Than the rule becomes "a function is always
> executed in a pseudo-subtransaction that affects only GUCs"

Only if it has at least one SET clause.  The overhead is too high
to insist on this for every function call.

			regards, tom lane