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. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
