[
https://issues.apache.org/jira/browse/DERBY-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633017#comment-13633017
]
Mike Matrigali commented on DERBY-6135:
---------------------------------------
In your example can you run compress database and get any/all space back? Just
trying to understand if in your case the compression would
be working around known issues with reclaiming space in the database. Also
good to know some more detail about your case, is the space
being used in seg0 or log?
Something that I think could be done pretty easily in Derby is to add
compression at the datatype level, rather than page level. Adding this for
blob, clob, and the character types would be interesting. Not sure what
syntax. Could do it at db level like encryption, or at column level with
new ddl.
There tends not to be standards in the ddl. Are there any db's that allow
compression indication at the colun level, and if so what syntax?
> Request data compression scheme (i.e., gzip of data pages)
> ----------------------------------------------------------
>
> Key: DERBY-6135
> URL: https://issues.apache.org/jira/browse/DERBY-6135
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Reporter: Tony Brusseau
>
> This is a request for a data compression scheme facility added to Derby
> (something like gzip of data pages). MySQL and some other databases provide
> such a feature, see:
> http://dev.mysql.com/doc/innodb-plugin/1.0/en/innodb-compression-internals.html
> The desire for this is because my current database size is 27GB but gzipped,
> it goes down to 7GB. I wish to scale my database dramatically, but the
> current disk footprint would prevent me from being able to use Derby.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
