Re: Advisory locks seem rather broken - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Advisory locks seem rather broken
Date
Msg-id CA+TgmoaL5MbKSgXvMb_huQ_YznBtq1NhLw3w1q5XGzMYPsEL3Q@mail.gmail.com
Whole thread Raw
In response to Re: Advisory locks seem rather broken  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Advisory locks seem rather broken
List pgsql-hackers
On Thu, May 3, 2012 at 3:52 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I'm inclined to say that you can PREPARE if your session holds a given
> advisory lock at either session or transaction level, but not both.
> This is a bit annoying but doesn't seem likely to be a real problem in
> practice, so thinking of a hack to support the case seems like more
> work than is justified.

I'd be more inclined to say that if you have a session-level lock, you
can't prepare, period.  Doesn't a rollback release session-level
locks?

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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: CLOG extension
Next
From: Daniel Farina
Date:
Subject: Re: CLOG extension