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:49:20 UTC
[jira] Created: (DERBY-691) committed deleted row space reclamation may be missed if delete is actually an aborted insert.
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
Reporter: Mike Matrigali
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
[jira] Updated: (DERBY-691) committed deleted row space reclamation
may be missed if delete is actually an aborted insert.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-691?page=all ]
Mike Matrigali updated DERBY-691:
---------------------------------
Description:
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.
was: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).
> 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).
> 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.
-
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
[jira] Updated: (DERBY-691) committed deleted row space reclamation
may be missed if delete is actually an aborted insert.
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-691) committed deleted row space reclamation
may be missed if delete is actually an aborted insert.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-691?page=all ]
Kathey Marsden updated DERBY-691:
---------------------------------
Attachment: autoloading_scenarios.html
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: http://issues.apache.org/jira/browse/DERBY-691
> Project: Derby
> Type: Improvement
> Components: Store
> Versions: 10.0.2.0
> Reporter: Mike Matrigali
> Priority: Minor
> Attachments: autoloading_scenarios.html
>
> 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.
-
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
[jira] Updated: (DERBY-691) committed deleted row space reclamation
may be missed if delete is actually an aborted insert.
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-691?page=all ]
Andrew McIntyre updated DERBY-691:
----------------------------------
Attachment: (was: autoloading_scenarios.html)
> 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).
> 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.
-
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
[jira] Commented: (DERBY-691) committed deleted row space reclamation may be missed if delete is actually an aborted insert.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-691?page=comments#action_12357061 ]
Mike Matrigali commented on DERBY-691:
--------------------------------------
This is project is not straight forward as the code that executes to mark the row deleted during an abort is at a much lower level then the current code which queues post commit committed deleted work.
> 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
> Reporter: Mike Matrigali
>
> 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
[jira] Updated: (DERBY-691) committed deleted row space reclamation may be missed if delete is actually an aborted insert.
Posted by "Mike Matrigali (JIRA)" <de...@db.apache.org>.
[ 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