Re: Controlling changes in plpgsql variable resolution

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: Controlling changes in plpgsql variable resolution
Дата
Msg-id 162867790910200913o6d119fect7d80b6f466afa030@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Controlling changes in plpgsql variable resolution  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Controlling changes in plpgsql variable resolution  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
2009/10/20 Tom Lane <tgl@sss.pgh.pa.us>:
> 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.

I don't thing, so drop some implicit-casts was huge problem. Somebody
could to use Peter's patch, that recreate missing casts.

regards
Pavel
>
>                        regards, tom lane
>


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Could postgres be much cleaner if a future release skipped backward compatibility?
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: Re: Application name patch - v2