Re: BUG #8290: broken/unexpected locking behavior - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #8290: broken/unexpected locking behavior
Date
Msg-id 20130709205357.GI18471@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: BUG #8290: broken/unexpected locking behavior  (Jamey Poirier <jpoirier@exagrid.com>)
Responses Re: BUG #8290: broken/unexpected locking behavior
List 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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #8289: pg_stat_statements incorrect query text when executing multiple queries in a single PQexec
Next
From: lalbin@fhcrc.org
Date:
Subject: BUG #8291: postgres_fdw does not re-read USER MAPING after change.