[
https://issues.apache.org/jira/browse/DERBY-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225625#comment-14225625
]
ASF subversion and git services commented on DERBY-4057:
--------------------------------------------------------
Commit 1641753 from mi...@apache.org in branch 'code/trunk'
[ https://svn.apache.org/r1641753 ]
DERBY-6774
org.apache.derbyTesting.functionTests.tests.lang.AlterTableTest.testAddIdentityColumn
failed with assert in nightlys
Temporarily removing assert that is failing, looks like code should handle
the condition anyway. Will renable after figuring out what is going on,
hoping this will allow for clean runs from others while I work on this issue.
My current theory is that there is a long time problem with alter table
and the conglomerate cache that has been uncovered by this relatively new
test and the new background work introduced by DERBY-4057.
> 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: Improvement
> Components: Store
> Affects Versions: 10.5.1.1
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
> Labels: derby_backport_reject_10_11, 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)
