
> Well, the proposal of implementing it like holdable cursors means using
> a Materialize node which, if I understand correctly, means taking the
> whole result set and storing it on memory (or disk).

Would it help to hold the lock for a record that is the current cursor position,
iff this record was updated (and subsequently rolled back) by this subtxn,
and release that lock as soon as you fetch next ?

Andreas

Tue, 6 Jul 2004 10:11:03 +0200
"Zeugswetter Andreas SB SD" <ZeugswetterA@spardat.at>
Re: subtransactions and FETCH behaviour (was Re: PREPARE and
	transactions)