| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch |
| Date: | 2007-02-08 20:40:01 |
| Message-ID: | 20070208204001.GH24069@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-08 21:03:14 | Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch |
| Previous Message | Alvaro Herrera | 2007-02-08 20:36:11 | Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2007-02-08 20:53:17 | Re: Feature: POSIX Shared memory support |
| Previous Message | Alvaro Herrera | 2007-02-08 20:36:11 | Re: [PATCHES] [pgsql-patches] Phantom Command IDs, updated patch |