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 Mon, 24 Nov 2014 16:38:12 GMT

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

ASF subversion and git services commented on DERBY-4057:

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

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

Added infrastructure called at insert abort time to queue post abort work.
After the abort work is queued in the case of aborted inserts to reclaim
space and if possible mark pages free, which then in turn allows them to
be used by subsequent work on the table.  This work queues this work
on heap tables when the aborted insert is the last row on a page, or
if the aborted insert is a row that contains a long column (a row that
is bigger than a page - usually a blob or clob), or a long row (a row
that spans multiple pages).

> 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