Re: BUG #8290: broken/unexpected locking behavior

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Jamey Poirier <jpoirier(at)exagrid(dot)com>
Cc: "pgnube(at)gmail(dot)com" <pgnube(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8290: broken/unexpected locking behavior
Date: 2013-07-09 20:53:57
Message-ID: 20130709205357.GI18471@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jamey Poirier escribió:
>
> Thank you Alvaro. Yes, this explains it.
> It doesn't help to fix it but at least I know now that it's a known "feature".
> I'll have to see about coming up with a work-around as we likely won't get to 9.3 anytime soon.

Perhaps you can use FOR SHARE instead of FOR UPDATE in the first
connection, for instance ..

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message lalbin 2013-07-09 22:05:20 BUG #8291: postgres_fdw does not re-read USER MAPING after change.
Previous Message Tom Lane 2013-07-09 19:20:56 Re: BUG #8289: pg_stat_statements incorrect query text when executing multiple queries in a single PQexec