Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch
Date
Msg-id 20070208204001.GH24069@alvh.no-ip.org
Whole thread Raw
In response to Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Alvaro Herrera wrote:

> This starts to look awfully similar to MultiXactIds.  And probably using
> such a mechanism would allow you to "rollback" any number of row locks:
> take the current membersoof the "multicid", substract the one that
> rolled back and use that as new multicid.  The main difference is that
> you'd need to store both the locker Cid and the mode (shared/exclusive).

Humm, sorry, obviously this makes no sense at all because I mentally
mixed the Xid locker and the Cids.

> The other difference is that multicids can be stored locally to a
> backend, no need to have SLRUs etc.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch