View Single Post

   
  #8 (permalink)  
Old 04-15-2008, 09:49 PM
Tom Lane
 
Posts: n/a
Default 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

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Reply With Quote