From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Kevin.Grittner@wicourts.gov
Cc: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
Cc: pgsql-hackers@postgresql.org
Subject: Re: SSI bug?
Date: Mon, 14 Feb 2011 12:40:37 +0200
Message-ID: <4D5906A5.8040602@enterprisedb.com> (raw)
In-Reply-To: <20110214050924.2E5E119CE7A@mail.netbsd.org>
References: <4D566A08020000250003A90B@gw.wicourts.gov>
<20110214050924.2E5E119CE7A@mail.netbsd.org>
Looking at the prior/next version chaining, aside from the looping
issue, isn't it broken by lock promotion too? There's a check in
RemoveTargetIfNoLongerUsed() so that we don't release a lock target if
its priorVersionOfRow is set, but what if the tuple lock is promoted to
a page level lock first, and PredicateLockTupleRowVersionLink() is
called only after that? Or can that not happen because of something else
that I'm missing?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: heikki.linnakangas@enterprisedb.com, Kevin.Grittner@wicourts.gov, yamt@mwd.biglobe.ne.jp
Subject: Re: SSI bug?
In-Reply-To: <4D5906A5.8040602@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox