Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Date
Msg-id CA+TgmoYVHWq3Bdd-+X=BiSBgHQMkNE6krLWZvQ8ibXaQzRhrQw@mail.gmail.com
Whole thread Raw
In response to Re: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block  (David Johnston <polobo@yahoo.com>)
List pgsql-hackers
Tree view 
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 by date:

Previous
From: Robert Haas
Date:
Subject: Re: shared memory message queues
Next
From: Tom Lane
Date:
Subject: Re: Review: pre-commit triggers