At 09:09 AM 4/11/2004 -0500, you wrote:

>:: Sorry, that doesn't make any sense. If the SELECT is in a
>:: read-only transaction, then the update statement has to be
>:: in a different transaction
>:: - a read-write one. You can't perform updates in a read-only
>:: transaction: an update is a write.
>
>Assuming it was readcommitted, but with a write option.

Huh? A read-only transaction with a write option?

A read-only transaction, readcommitted transaction doesn't hold up the
cleanup of the TSB, that's the point. As soon as you make it read-write,
it will hold up the housekeeping until it gets a hard commit. Obviously,
you don't run select statements to do anything but just look at them, i.e.
to use some id's as selectors, if I recall your scenario. So use a
read-only transaction to do the looking and selecting, and pass the values
selected to the parameter(s) of your update statement in the read-write
transaction.

./hb