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

From Robert Haas
Subject Re: SSI predicate locking on heap -- tuple or row?
Date
Msg-id BANLkTi=vG-ZfLDtGbekRvrCgr85YDdXVyg@mail.gmail.com
Whole thread Raw
In response to SSI predicate locking on heap -- tuple or row?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Sat, May 21, 2011 at 4:09 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
> [Anyone who has followed along this far has earned my undying
> gratitude.]
>
> Since the chain of transactions has to overlap T0 and T3, I don't see
> how that can happen.  We established that T0 has to commit before T3 can
> start, so the chain will ultimately have to get to that T0 commit.
>
> I don't want to start ripping out the apparently useless code without
> someone checking my logic here.  One big gaff in this area is quite
> enough for me.  :-/  Anyone?

How is an UPDATE different from a DELETE and an INSERT?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: eviscerating the parser
Next
From: Robert Haas
Date:
Subject: Re: eviscerating the parser