db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-509) DERBY-132 resolved ? Table not automatically compressed
Date Tue, 16 Aug 2005 22:19:55 GMT
    [ http://issues.apache.org/jira/browse/DERBY-509?page=comments#action_12318940 ] 

Jean T. Anderson commented on DERBY-509:
----------------------------------------

This seems to me like it would be an excellent question for derby-user@db.apache.org. Could
you repost it there? That way others on that list will also benefit from the reply.

I realize sometimes it isn't obvious how to post to the derby lists. First you need to subscribe
by sending email to:

  derby-user-subscribe@db.apache.org

The first time you post to that list there will be a delay because the first post is moderated.
Later posts will automatically hit the list.

More information about the derby lists is here:
   http://db.apache.org/derby/derby_mail.html

> DERBY-132 resolved ? Table not automatically compressed
> -------------------------------------------------------
>
>          Key: DERBY-509
>          URL: http://issues.apache.org/jira/browse/DERBY-509
>      Project: Derby
>         Type: Bug
>     Versions: 10.1.1.0
>  Environment: JDK 1.4.2, JDK 1.5.0,
> Windows XP
>     Reporter: Volker Edelmann

>
> I tried a test-program that repeatedly inserts a bunch of  data into 1 table and repeatedly
deletes a bunch of data. 
>     	derby.executeSelect("select count(*) c from rclvalues");	
>   	TestQueries.executeBulkInsertAnalyst(derby.getConnection(), 2000000);  // insert 2.000.000
rows
>         derby.executeDelete("delete from rclvalues where MOD(id, 3) = 0");          
  
>   	TestQueries.executeBulkInsertAnalyst(derby.getConnection(), 1000000);
>         derby.executeDelete("delete from rclvalues where MOD(id, 5) = 0");
>     	derby.executeSelect("select count(*) c from rclvalues");
> At the end of the operation, the table contains approximately the same number of rows.
But the size of the database  has grown  from
> 581 MB to 1.22 GB. From the description of item DERBY-132, I hoped that Derby does the
compression now ( version 10.1.X.X.).
> Did I overlook I still have to use  SYSCS_UTIL.SYSCS_COMPRESS_TABLE ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message