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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Brendan Jurd" <direvus(at)gmail(dot)com>
Cc: "Michael Paesold" <mpaesold(at)gmx(dot)at>, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Per-function GUC settings: trickier than it looked
Date: 2007-09-05 03:52:44
Message-ID: 28620.1188964364@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> So, if I read you correctly, in summary we'd like to:

> * make SET LOCAL local to the transaction (i.e., make it behave as documented),
> * abandon the idea of a subtransaction-local SET, because the new
> function-local SET takes care of the interesting use-cases for that,
> * somehow deal with the incompatibility with the 8.2 "security
> definer" workaround.

> Tom's proposal to handle the latter was that when a function-local SET
> reverts, it overrides any inner SET LOCALs.

> Am I on the right page?

Got it in one, I believe.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-09-05 04:06:52 Re: HEAD build troubles, buildfarm misconfigurations
Previous Message Robert Treat 2007-09-05 03:52:08 HEAD build troubles, buildfarm misconfigurations