Re: Rethinking the parameter access hooks for plpgsql's benefit

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Rethinking the parameter access hooks for plpgsql's benefit
Дата
Msg-id 29654.1426701701@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Rethinking the parameter access hooks for plpgsql's benefit  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: Rethinking the parameter access hooks for plpgsql's benefit  (Robert Haas <robertmhaas@gmail.com>)
Re: Rethinking the parameter access hooks for plpgsql's benefit  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> Seriously? In my opinion it has to be possible to doubt whether a patch
> should be committed in certain release without it being interpreted as a
> personal attack.

I don't think anyone's said anything in this thread that amounts to a
personal attack.  We have a difference of opinion on policy, and what
I'm saying is that the policy ultimately reduces to trusting individual
committers to use their best judgment.  If someone's going to tell me
that my judgment about when to push something is not acceptable, then
they probably ought to be calling for removal of my commit privileges.
        regards, tom lane



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Strange assertion using VACOPT_FREEZE in vacuum.c
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Add LINE: hint when schemaname.typename is a non-existent schema