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

From Marko Kreen
Subject Re: Per-function search_path => per-function GUC settings
Date
Msg-id e51f66da0709011537g34bc45c5g5169ffe49c92f7c7@mail.gmail.com
Whole thread Raw
In response to Re: Per-function search_path => per-function GUC settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Per-function search_path => per-function GUC settings
List pgsql-hackers
On 9/1/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jeff Davis <pgsql@j-davis.com> writes:
> > Can we also provide syntax which would be equivalent to setting "var"
> > for the function to be whatever the current value happens to be when the
> > ALTER FUNCTION is run? Possible syntax might be something like:
>
> > ALTER FUNCTION func(args) SET var TO CURRENT;
>
> Hmmm ... that's certainly do-able, though I'm not sure how much it helps
> the use-case you suggest.  The search path still has to be set at the
> top of the module script, no?
>
> However, I like an explicit option of this sort a lot better than the
> automatic version Greg was suggesting ... I'm willing to do it if people
> want it.
>
> One problem is that we'd have to make CURRENT a reserved word to make it
> work exactly like that.  Can anyone think of a variant syntax that
> doesn't need a new reserved word?

SET var FROM CURRENT SESSION

-- 
marko


pgsql-hackers by date:

Previous
From: Decibel!
Date:
Subject: Re: Per-function search_path => per-function GUC settings
Next
From: David Fetter
Date:
Subject: Re: Per-function search_path => per-function GUC settings