db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@apache.org>
Subject Re: conflict detection strategies
Date Wed, 15 Feb 2006 14:19:54 GMT
Andreas Korneliussen wrote:

> Problem:
> For holdable cursors, we will release the table intent lock when doing
> commit on the transaction for the cursor.
> The table intent lock, prevents the system from doing a compress of the
> table, causing all RowLocations to be invalid. In addition, it prevents
> reuse of RowLocation for deleted + purged rows.

I think this last paragraph is an incorrect assuption. The table intent
lock prevents other transactions from doing a compress, but not the
transaction holding the lock.

I think there are other situations where the RowLocation will become
invalid, such as the transaction deleteing the row.


View raw message