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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/06/02 15:51:37 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=12874581#action_12874581 ]
Kristian Waagan commented on DERBY-4054:
----------------------------------------
Is BLOB affected by this problem as well?
> 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
>
> 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.