db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4057) Space is not reclaimed if transaction is rolled back
Date Tue, 25 Nov 2014 04:24:12 GMT

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

ASF subversion and git services commented on DERBY-4057:

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

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

a few changes to make the ClobReclamationTest better behaved across a variety
of platforms.  The test tries to measure background thread behavior, and needs
to allow for machines/jvms that might be single threaded and slow.  

In one case added a sleep after all aborts to allow the background thread
to catch up and mark all pages but head one free.  

In other case added more to the fudge factor of how much immediate insert
might progress before background thread can catch up and make free page 
available.  If this does not work may just need to add sleep after every 

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

View raw message