db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-4057) Space is not reclaimed if transaction is rolled back
Date Wed, 12 Nov 2014 23:34:34 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-4057:
----------------------------------
    Issue Type: Improvement  (was: Bug)

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

Mime
View raw message