Re: Per-function search_path => per-function GUC settings - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Per-function search_path => per-function GUC settings
Date
Msg-id 7939.1188749479@sss.pgh.pa.us
Whole thread Raw
In response to Re: Per-function search_path => per-function GUC settings  ("Marko Kreen" <markokr@gmail.com>)
Responses Re: Per-function search_path => per-function GUC settings
Re: Per-function search_path => per-function GUC settings
List pgsql-hackers
"Marko Kreen" <markokr@gmail.com> writes:
> On 9/2/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Seems a little verbose, but maybe we could do "SET var FROM CURRENT"
>> or "SET var FROM SESSION"?

> I'd prefer FROM SESSION then.  FROM CURRENT seems unclear.

Actually, I think FROM SESSION is unclear, as it opens the question
whether the value to be applied is the session-wide setting or the
currently active one.  Inside a transaction that has done SET LOCAL,
these are different things.

I think we pretty clearly want to have it take the currently active
setting, and I'd vote for FROM CURRENT as the best way of expressing
that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Per-function GUC settings: trickier than it looked
Next
From: Jeff Davis
Date:
Subject: Re: Per-function search_path => per-function GUC settings