[jira] Commented: (DERBY-4639) Repeatedly issuing a CREATE TABLE against a table that already exists causes Derby to soak up disk space

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen commented on DERBY-4639:
-------------------------------------------

I see this too when I follow the steps described above. It looks like the space is reclaimed on a clean shutdown of the database or if a checkpoint is invoked.

> Repeatedly issuing a CREATE TABLE against a table that already exists causes Derby to soak up disk space
> --------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4639
>                 URL: https://issues.apache.org/jira/browse/DERBY-4639
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.3.0
>            Reporter: David Van Couvering
>
> Create a program that issues CREATE TABLE against an existing table every five seconds, ignoring the exception that the table already exists.  
> Observe that the database directory starts growing by about 1 MB every minute.  You can also see the number of .dat files growing in seg0 at a constant rate.
> Workaround is to check to see if the table exists first before issuing the CREATE TABLE statement, but this is still a bug.

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