committed deleted row space reclamation may be missed if delete is actually an aborted insert.

• Key: DERBY-691
• Type: Improvement
• Status: Open
• Priority: Minor
• Assignee: Unassigned
• Reporter: Mike Matrigali
• Component/s: Store
• Affects Version/s: 10.0.2.0

Description

The system should queue post commit activity in the case of an aborted insert which internally is implemented as a delete. In this case post commit should be queued following the same rules as straight line delete currently. The result is that if the last delete on a page is actually an aborted insert then space on that page may never be automatically reclaimed (It is always can be reclaimed by hand using the space reclamation system procedures).

Note that a duplicate key insert error internally generates this case. It first inserts the row into the base table. Then it attempts to insert a row into the unique index and fails. As part of the failure it aborts the statement which turns the insert into a delete as part of the undo.

Comments

[Mike Matrigali]

This is project is not straight forward as the code that executes to mark the row deleted during an abort is at a much lower level then the current code which queues post commit committed deleted work.

[Kathey Marsden]

Document desribing scenarios that need to be handled by autoloading.