Re: Per-function GUC settings: trickier than it looked - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Per-function GUC settings: trickier than it looked
Date
Msg-id 12914.1188837780@sss.pgh.pa.us
Whole thread Raw
In response to Re: Per-function GUC settings: trickier than it looked  ("Florian G. Pflug" <fgp@phlo.org>)
Responses Re: Per-function GUC settings: trickier than it looked
List pgsql-hackers
"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


pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Per-function GUC settings: trickier than it looked
Next
From: "Trevor Talbot"
Date:
Subject: Re: tsearch filenames unlikes special symbols and numbers