Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 5 Dec 2014 22:38:12 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12414759.1234542829000.89036.1417819092921@Atlassian.JIRA>
In-Reply-To: <JIRA.12414759.1234542829000@Atlassian.JIRA>
References: <JIRA.12414759.1234542829000@Atlassian.JIRA>
 <JIRA.12414759.1234542829435@arcas>
Subject: [jira] [Commented] (DERBY-4057) Space is not reclaimed if
 transaction is rolled back
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236237#comment-14236237 ] 

ASF subversion and git services commented on DERBY-4057:
--------------------------------------------------------

Commit 1643463 from mikem@apache.org in branch 'code/trunk'
[ https://svn.apache.org/r1643463 ]

DERBY-4057

Removing one check in test that is failing across platforms.  Separate
work under DERBY-6775 will improve the test in this area.

> 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)