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-02 15:42:08 |
Message-ID: | e51f66da0709020842l1ee5040er317a0eb525e3a74c@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9/2/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Marko Kreen" <markokr(at)gmail(dot)com> writes:
> > On 9/1/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> 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
>
> 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.
> One point worth noting here is that this'd more or less automatically
> apply to ALTER USER SET and ALTER DATABASE SET as well ... not sure
> how much use-case there is for those, but it'd fall out ...
Does not seem to be a problem.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-09-02 16:08:00 | Re: Per-function GUC settings: trickier than it looked |
Previous Message | Tom Lane | 2007-09-02 15:20:56 | Re: GIST and GIN indexes on varchar[] aren't working in CVS. |