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

["Mike Matrigali (Updated) (JIRA)" <ji...@apache.org>]

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

Mike Matrigali updated DERBY-4054:
----------------------------------

    Labels: derby_triage10_5_2 derby_triage10_9  (was: derby_triage10_5_2)

derby 10.9 triage.  no changes.
                
> 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.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.1.1
>            Reporter: Kathey Marsden
>              Labels: derby_triage10_5_2, derby_triage10_9
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira