Re: plpgsql GUC variable: custom or built-in?

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: plpgsql GUC variable: custom or built-in?
Дата
Msg-id 603c8f070911120826y29c1de3alc68288cdca1f1106@mail.gmail.com
обсуждение исходный текст
Ответ на plpgsql GUC variable: custom or built-in?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: plpgsql GUC variable: custom or built-in?
Список pgsql-hackers
On Thu, Nov 12, 2009 at 11:13 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> One reason to argue for the other way is that maybe it wouldn't only
> be consulted by plpgsql.  In particular I can easily imagine SQL
> functions having the same issue as soon as someone gets around to
> letting them use names for their parameters.

I don't have a strong feeling on the core issue but I don't agree with
this point.  AIUI, we are implementing multiple behaviors here for
reasons of backward and competing-product compatibility.  Presumably,
if we're starting from scratch, we'll pick a sensible behavior -
probably error in the case of SQL - and stick with it.

...Robert


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

Предыдущее
От: Andrew Chernow
Дата:
Сообщение: Re: Listen / Notify rewrite
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Listen / Notify rewrite