Re: Controlling changes in plpgsql variable resolution

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: Controlling changes in plpgsql variable resolution
Дата
Msg-id 4ADC6475020000250002BB36@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: Controlling changes in plpgsql variable resolution  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> wrote:
> (a) Nobody but me is afraid of the consequences of treating this as
> a GUC.
Well, it seems dangerous to me, but I'm confident we can cover this
within our shop, so I'm reluctant to take a position on it.  I guess
the main question is whether we want to allow an Oracle-compatibility
mode, knowing it's a foot-gun.  Without it we'd likely make extra work
for someone converting from Oracle to PostgreSQL, although they would
be likely to fix bugs during the cleanup work.  Based on previous
decisions I've seen here, I would have expected people to just go with
an error, period; especially since it would simplify the code.
> (b) Everybody agrees that a "throw error" setting would be helpful.
That's the only setting I would use on any of our databases, if it
were a GUC.
-Kevin


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Controlling changes in plpgsql variable resolution
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: Controlling changes in plpgsql variable resolution