Re: SSI predicate locking on heap -- tuple or row? - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: SSI predicate locking on heap -- tuple or row?
Date
Msg-id 4DE8B1A8.2020505@enterprisedb.com
Whole thread Raw
In response to Re: SSI predicate locking on heap -- tuple or row?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On 03.06.2011 00:14, Kevin Grittner wrote:
> Attached is a comments-only patch for this, along with one
> correction to  the comments you added and a couple other typos.

Ok, committed.

> I'll submit a patch for the README-SSI file once I find a reference
> I like to a paper describing what Dan's proof uses as a premise --
> that the transaction on the rw-conflict *out* side of the pivot must
> not only be the first of the three transactions in the dangerous
> structure to commit, but the first in the entire cycle of which the
> dangerous structure is a part.  With that premise as a given, the
> proof is short, clear, and unassailable; but I think we need a cite
> to use that argument convincingly.

Agreed.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: storing TZ along timestamps
Next
From: Alexander Korotkov
Date:
Subject: WIP: Fast GiST index build