db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-691) committed deleted row space reclamation may be missed if delete is actually an aborted insert.
Date Fri, 18 Jun 2010 17:41:26 GMT

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

Kathey Marsden updated DERBY-691:
---------------------------------

    Comment: was deleted

(was: Document desribing scenarios that need to be handled by autoloading.)

> committed deleted row space reclamation may be missed if delete is actually an aborted
insert.
> ----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-691
>                 URL: https://issues.apache.org/jira/browse/DERBY-691
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.0.2.0
>            Reporter: Mike Matrigali
>            Priority: Minor
>
> The system should queue post commit activity in the case of an aborted insert which internally
is implemented as a delete.  In this case post commit should be queued following the same
rules as straight line delete currently.  The result is that if the last  delete on a page
is actually an aborted insert then space on that page may never be automatically reclaimed
(It is always can be reclaimed by hand using the space reclamation system procedures).
> Note that a duplicate key insert error internally generates this case.  It first inserts
the row into the base table.  Then it attempts to insert a row into the unique index and fails.
 As part of the failure it aborts the statement which turns the insert into a delete as part
of the undo.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message