Re: BUG #8290: broken/unexpected locking behavior

From: pg noob <pgnube(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Jamey Poirier <jpoirier(at)exagrid(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-10 15:14:07
Message-ID: CAPNY-2UXTGD9LSoK14_JjZNQgqf56K_eX36krq1t34UfZYBA8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)2ndquadrant(dot)com>wrote:

> 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 Josh Kupershmidt 2013-07-10 15:17:06 Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist
Previous Message Pavel Stehule 2013-07-10 15:06:18 Re: [BUGS] BUG #7873: pg_restore --clean tries to drop tables that don't exist