Re: Controlling changes in plpgsql variable resolution

Merlin Moncure <mmoncure@gmail.com> writes:
> How about warning for release before making the big switch?  The text
> cast change, while ultimately good, maybe could have been stretched
> out for a release or two...it was painful.  I do though absolutely
> think that it was good in the end to not support a compatibility
> option in core.

As long as we provide a backwards-compatible setting, I don't believe
this change will be a huge deal.  The problem with the implicit-casts
business was that there was no reasonable way to provide a control
switch --- the catalog entries were either there or not :-(.  So far
as I can tell at the moment, there won't be any large technical cost
to providing a backwards-compatible option for this plpgsql change.
        regards, tom lane