Date: Wed, 14 Nov 2012 13:27:26 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: foreign key locks
Message-ID: <20121114162726.GE5161@alvh.no-ip.org>
References: <4FEAB90A0200002500048B7D@gw.wicourts.gov>
	<1346389151-sup-8379@alvh.no-ip.org>
	<20121018195820.GO3763@alvh.no-ip.org>
	<201210270006.54728.andres@2ndquadrant.com>
	<20121114152347.GA5161@alvh.no-ip.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20121114152347.GA5161@alvh.no-ip.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Content-Transfer-Encoding: quoted-printable

Alvaro Herrera wrote:

> > * In heap_lock_tuple's  XMAX_IS_MULTI case
> >=20
> > [snip]
> >=20
> > why is it membermode > mode and not membermode >=3D mode?
>=20
> Uh, that's a bug.  Fixed.  As noticed in the comment above that snippet=
,
> there was a deadlock possible here.  Maybe I should add a test to ensur=
e
> this doesn't happen.

Done:
https://github.com/alvherre/postgres/commit/df2847e38198e99f57e52490e1e93=
91ebb70d770

(I don't think this is worth a v24 submission).

--=20
=C1lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services