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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2009/02/12 19:15:59 UTC

[jira] Commented: (DERBY-4054) Multithreaded clob update with exclusive table locking causes table growth that is not reclaimed

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

Kathey Marsden commented on DERBY-4054:
---------------------------------------

Committed a test that demonstrates the issue  with revision  743820 store/ClobReclamationTest.xtestMultiThreadedUpdateTableLocking()
Enable this test to reproduce the problem.

 

> Multithreaded clob update with exclusive table locking causes table growth that is not reclaimed
> ------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4054
>                 URL: https://issues.apache.org/jira/browse/DERBY-4054
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.5.0.0
>            Reporter: Kathey Marsden
>
> If I do a multithreaded clob update which gets an exclusive table lock on the table, space will not be reclaimed.  This case is similar to DERBY-4050 except that the test gets an exclusive table lock and the growth happens whether or not the update is synchronized.  I will add a disabled test for this to ClobReclamationTest and reference this bug.    

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