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

From Brendan Jurd
Subject Re: Per-function GUC settings: trickier than it looked
Date
Msg-id 37ed240d0709042113y302ba32p43a5aa49c2b7c854@mail.gmail.com
Whole thread Raw
In response to Re: Per-function GUC settings: trickier than it looked  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Per-function GUC settings: trickier than it looked
List pgsql-hackers
On 9/5/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Brendan Jurd" <direvus@gmail.com> writes:
> > Am I on the right page?
>
> Got it in one, I believe.

In that case, +1 for your proposed changes.

At first, like Florian, I found the idea of a SET LOCAL ever
persisting beyond a function astonishing, but that's because I was
approaching the term LOCAL from a programming frame of mind, not an
SQL one.  Once you appreciate that LOCAL means local to the
transaction, rather than local to the programming context, it all
makes sense.

Cheers,
BJ


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: HEAD build troubles, buildfarm misconfigurations
Next
From: Tom Lane
Date:
Subject: Re: HEAD build troubles, buildfarm misconfigurations