| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Controlling changes in plpgsql variable resolution |
| Date: | 2009-10-19 18:55:27 |
| Message-ID: | CB66B656-C6DB-42C4-B70D-78DB0631D49F@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 19, 2009, at 11:47 AM, Tom Lane wrote:
> 1. Invent a GUC that has the settings backwards-compatible,
> oracle-compatible, throw-error (exact spellings TBD). Factory
> default,
> at least for a few releases, will be throw-error. Make it SUSET so
> that
> unprivileged users can't break things by twiddling it; but it's still
> possible for the DBA to set it per-database or per-user.
>
> 2. Also invent a #option syntax that allows the GUC to be overridden
> per-function. (Since the main GUC is SUSET, we can't just use a
> per-function SET to override it. There are other ways we could do
> this
> but none seem less ugly than #option...)
What about adopting the modifier syntax you're adding to COPY?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-10-19 19:05:14 | Re: Controlling changes in plpgsql variable resolution |
| Previous Message | Tom Lane | 2009-10-19 18:47:28 | Re: Controlling changes in plpgsql variable resolution |