[DERBY-4057] Space is not reclaimed if transaction is rolled back

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.5.1.1
• Fix Version/s: 10.12.1.1
• Component/s: Store
• Labels: derby_backport_reject_10_11 derby_triage10_5_2 derby_triage10_9
• Urgency: Normal
• Assignee: Mike Matrigali
• Reporter: Katherine Marsden
• Created: 13/Feb/09 16:33
• Updated: 09/Sep/16 09:54
• Resolved: 11/Dec/14 16:54

Description

If I repeatedly insert into a clob table and rollback the the transaction the space is not reclaimed and the number of allocated pages continues to grow. I will add a test case to ClobReclamationTest and reference this bug.

DERBY-4056 may be a special case of this bug, but I thought I would file a bug for the general issue.

Issue Links

• is part of: DERBY-691 committed deleted row space reclamation may be missed if delete is actually an aborted insert.
• is related to: DERBY-4050 Multithreaded clob update causes growth in table that does not get reclaimed
• is related to: DERBY-6774 background post commit threads cause ASSERTS/errors on interaction with alter table add column
• is related to: DERBY-6775 add to testBlobLinkedListReclamationOnRollback() test to check that free space is used on subsequent inserts
• is related to: DERBY-5356 Tracking for Derby space reclamation issues
• relates to: DERBY-4056 Space is not reclaimed when attempting to insert row that violates UNIQUE constraint