[
https://issues.apache.org/jira/browse/DERBY-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4057:
----------------------------------
Attachment: DERBY-4057_patch_2.diff
This patch is an improvement over the previous initial prototype. It
passes all tests on my machine, ibm17, windows except for
testBlobLinkedListReclamationOnRollback. And that test just needs to
get changed to expect the improved reclamation, after the patch table
is left with 1 allocated page rather than 1000.
I expect to post one more patch with comments cleaned up and making sure
debugging code is removed.
The major change in the approach to get a number of tests to pass was
to change the "in transaction" queueing code that creates the HeapPostCommit to
only take a PageKey rather than a Heap. This meant
the code did not interact with the conglomerate cache and possibly have
to do things like read data from the container during abort. This is the same
info that the raw store ReclaimSpace work item does. This solved
problems with alter table tests, interrupt tests, and AccessFactory unit tests.
only test error, which just needs to be changed to accept new behavior:
1) testBlobLinkedListReclamationOnRollback(org.apache.derbyTesting.functionTests
.tests.store.ClobReclamationTest)junit.framework.AssertionFailedError: Column va
lue mismatch @ column 'NUMALLOCATEDPAGES', row 1:
Expected: >1001<
Found: >1<
NUMALLOCATEDPAGES
-----------------
[1]
> Space is not reclaimed if transaction is rolled back
> ----------------------------------------------------
>
> Key: DERBY-4057
> URL: https://issues.apache.org/jira/browse/DERBY-4057
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.5.1.1
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
> Labels: derby_triage10_5_2, derby_triage10_9
> Attachments: DERBY-4057_initial_prototype_patch.diff,
> DERBY-4057_patch_2.diff
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
