You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <de...@db.apache.org> on 2005/11/08 20:51:20 UTC

[jira] Updated: (DERBY-691) committed deleted row space reclamation may be missed if delete is actually an aborted insert.

     [ http://issues.apache.org/jira/browse/DERBY-691?page=all ]

Mike Matrigali updated DERBY-691:
---------------------------------

    Component: Store
      Version: 10.0.2.0
     Priority: Minor  (was: Major)

> committed deleted row space reclamation may be missed if delete is actually an aborted insert.
> ----------------------------------------------------------------------------------------------
>
>          Key: DERBY-691
>          URL: http://issues.apache.org/jira/browse/DERBY-691
>      Project: Derby
>         Type: Improvement
>   Components: Store
>     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).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira