From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Jeff Davis" <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Per-function search_path => per-function GUC settings |
Date: | 2007-09-01 22:37:35 |
Message-ID: | e51f66da0709011537g34bc45c5g5169ffe49c92f7c7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/1/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Davis <pgsql(at)j-davis(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2007-09-01 22:52:29 | Re: Per-function search_path => per-function GUC settings |
Previous Message | Decibel! | 2007-09-01 22:23:55 | Re: Per-function search_path => per-function GUC settings |