Re: Notes on lock table spilling - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Notes on lock table spilling
Date
Msg-id 87acodq4o0.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Notes on lock table spilling  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
Responses Re: Notes on lock table spilling  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List pgsql-hackers
Alvaro Herrera <alvherre@dcc.uchile.cl> writes:

> Using Phantom Xids
> ==================
> The idea here is to use an approach similar to what we use now: mark the
> tuples with an Xid when it is locked.  A phantom Xid is a sort-of Xid,
> with multiple real Xids associated to it.  So we mark the tuple with the
> regular Xid the first time the share lock is acquired; if a second
> transaction wants to lock the tuple, it creates a new phantom Xid which
> "contains" the original Xid in the tuple and its own Xid, insert it into
> the phantom Xid table, and mark the tuple with that as Xmax.

That sounds like a fancy way to describe "make a linked list of lockers".

-- 
greg



pgsql-hackers by date:

Previous
From: "Greg Sabino Mullane"
Date:
Subject: Re: [GENERAL] plPHP in core?
Next
From: Greg Stark
Date:
Subject: Re: [GENERAL] plPHP in core?