Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
This issue is being used to track various Derby space reclamation issues.
Users have reported the need to do periodic compress due to these issues, so opening this issue for centralized tracking of the problem and also to help users identify which issue they are hitting and possible work arounds.
Attachments
Issue Links
- is duplicated by
-
DERBY-512 enhance existing automatic space reclamation for tables
- Closed
- relates to
-
DERBY-4054 Multithreaded clob update with exclusive table locking causes table growth that is not reclaimed
- Open
-
DERBY-4055 Space may not be reclaimed if row locks are not available after three retries
- Open
-
DERBY-5473 Index growth can occur with update of ever increasing values
- Open
-
DERBY-4050 Multithreaded clob update causes growth in table that does not get reclaimed
- Closed
-
DERBY-4056 Space is not reclaimed when attempting to insert row that violates UNIQUE constraint
- Closed
-
DERBY-3843 enhance SYSCS_INPLACE_COMPRESS_TABLE to better handle overflow rows and overflow columns
- Open
-
DERBY-1193 increase usage of "unfilled" pages after successful committed deleted purged rows.
- Open
-
DERBY-4057 Space is not reclaimed if transaction is rolled back
- Closed
-
DERBY-512 enhance existing automatic space reclamation for tables
- Closed
-
DERBY-670 improve space reclamation from deleted blob/clob columns which are bigger than a page
- Closed
-
DERBY-691 committed deleted row space reclamation may be missed if delete is actually an aborted insert.
- Closed