Ken Hirsch wrote: > From: "Bruce Momjian" <[EMAIL PROTECTED]> > > And finally, I must abort tuple changes made by the aborted > > subtransaction. One way of doing that is to keep all relation id's > > modified by the transaction, and do a sequential scan of the tables on > > abort, changing the transaction id's to a fixed aborted transaction id. > > However, this could be slow. (We could store tids if only a few rows > > are updated by a subtransaction. That would speed it up considerably.) > > Are you sure you don't want to use the log for this? It does mean that the > log can grow without bound for long-lived transactions, but it's very > straightforward and fast.
I don't think we want to have unlimited log file growth for long running transactions/subtransactions. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
