Re: Controlling changes in plpgsql variable resolution

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, 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>, "David E(dot) Wheeler" <david(at)kineticode(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-21 21:13:33
Message-ID: 603c8f070910211413h16ce0f28kd8544c291503e376@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 21, 2009 at 5:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I actually think that we should not have a GUC for this at all.  We
>> should have a compiled-in default, and it should be error.  If you
>> want some other behavior, decorate your functions with #option.
>
> We've agreed that the factory default should be "error", but I don't
> think we can go much further than that in the direction of breaking
> peoples' code.  We need to provide a backwards-compatible option,
> IMHO, so that this isn't seen as a roadblock to updating to 8.5.
> (You can argue all you want about whether it really is one, but it'll
> be seen as one.)

Hmm... I wouldn't see inserting a line at the beginning of every
function as a roadblock, but I don't rule out the possibility that I'm
thick-skinned.

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Itagaki Takahiro 2009-10-22 01:50:28 Re: Prelim specs for parser hooks for plpgsql
Previous Message Tom Lane 2009-10-21 21:13:23 Re: Controlling changes in plpgsql variable resolution