| 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 19:52:58 |
| Message-ID: | 7D5D166F-AEBE-4EBD-9058-A807EAEB296D@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 19, 2009, at 12:23 PM, Tom Lane wrote:
>> That is, the specification of options is made outside of the language
>> in question.
>
> I don't think I particularly care for this. It's inventing a global
> mechanism to cover a problem that we currently have one instance of
> in one PL. That's a mighty thin justification. Also, I tend to think
> that you should have several instances of a problem before you venture
> to design a global solution --- else your one-size-fits-all solution
> might turn out to be a lot less general than you thought.
Sure, just an idea to keep in mind for when you do have a second and a
third option to add…
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-10-19 20:34:57 | Re: Application name patch - v2 |
| Previous Message | Tom Lane | 2009-10-19 19:46:26 | Re: Controlling changes in plpgsql variable resolution |