db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4639) Repeatedly issuing a CREATE TABLE against a table that already exists causes Derby to soak up disk space
Date Thu, 17 Feb 2011 00:08:24 GMT

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

Dag H. Wanvik updated DERBY-4639:
---------------------------------

    Urgency: Normal
     Labels: derby_triage10_8  (was: )

> 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
>          Components: SQL
>    Affects Versions: 10.5.3.0
>            Reporter: David Van Couvering
>            Assignee: Lily Wei
>              Labels: derby_triage10_8
>         Attachments: CreateExistedTableDBGrow.java
>
>
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message