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

From pg noob
Subject Re: BUG #8290: broken/unexpected locking behavior
Date
Msg-id CAPNY-2UXTGD9LSoK14_JjZNQgqf56K_eX36krq1t34UfZYBA8Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #8290: broken/unexpected locking behavior  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
Alvaro,

Is there a PostgreSQL bug number that I could refer to for this problem?

Thank you.


On Tue, Jul 9, 2013 at 4:53 PM, Alvaro Herrera <alvherre@2ndquadrant.com>wr=
ote:

> Jamey Poirier escribi=F3:
> >
> > 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 ..
>
> --
> =C1lvaro Herrera                http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #8290: broken/unexpected locking behavior
Next
From: renzo_gch@hotmail.com
Date:
Subject: BUG #8292: Error en Una Función llamada desde NetBeans