On Fri, May 28, 2004 at 03:19:29PM -0400, Tom Lane wrote: > We'd still need a plain CommandCounterIncrement facility, which means > that actually a subtransaction would have to be a group of CIDs not just > one.
Right, this is why I suggested runlength (the group is contiguous). > So there'd also need to be a data structure showing the CIDs > associated with each open subtransaction --- this is what you'd > consult to go and set the "aborted" bits if the subxact rolls back. Right. We only need to store the "borders" though. Not even that: only the start, because the end is what is current at AbortSubTransaction() time. I'll try this. -- Alvaro Herrera (<alvherre[a]dcc.uchile.cl>) "El miedo atento y previsor es la madre de la seguridad" (E. Burke) ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
