db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Wooldridge (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6135) Request data compression scheme (i.e., gzip of data pages)
Date Thu, 02 Oct 2014 07:28:34 GMT

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

Brett Wooldridge commented on DERBY-6135:

I am also interested in this feature.  I am willing to put some working into an implementation.
 I was envisioning something like an additional keyword.  Obviously, it would be non-standard
(as there is no standard), something like:
I also imaging the best place to do this would be at the "page manager" level, but as this
would be new territory for me, tips, warnings, and caveats would be welcome.

> 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 was sent by Atlassian JIRA

View raw message