Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Дата
Msg-id CA+TgmoYVHWq3Bdd-+X=BiSBgHQMkNE6krLWZvQ8ibXaQzRhrQw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block  (David Johnston <polobo@yahoo.com>)
Список pgsql-hackers
On Mon, Nov 18, 2013 at 9:07 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Well, ERROR is what LOCK returns, so if we change SET TRANSACTION to be
> WARNING, we should change LOCK too, so on backward-compatibility
> grounds, ERROR makes more sense.
>
> Personally, I am fine with changing them all to WARNING.

I don't think it's worth breaking backward compatibility.  I'm not
entirely sure what I would have decided here in a vacuum, but at this
point existing precedent seems determinative.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: shared memory message queues
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Review: pre-commit triggers