Re: Controlling changes in plpgsql variable resolution - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Controlling changes in plpgsql variable resolution
Date
Msg-id 603c8f070910211413h16ce0f28kd8544c291503e376@mail.gmail.com
Whole thread Raw
In response to Re: Controlling changes in plpgsql variable resolution  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Oct 21, 2009 at 5:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Controlling changes in plpgsql variable resolution
Next
From: Itagaki Takahiro
Date:
Subject: Re: Prelim specs for parser hooks for plpgsql