[
https://issues.apache.org/jira/browse/COUCHDB-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081352#comment-13081352
]
Paul Joseph Davis commented on COUCHDB-1243:
--------------------------------------------
Though there's a caveat and a note on purge. Firstly, if you purge twice in a
row without updating a view, you have to rebuild the view from scratch. For
heavy users of views this becomes a problem. This is just an implementation
detail at the moment and at some time in the future could eventually be fixed.
And a note, there was another report of a bug this morning that looks as though
its triggered in the purge code and specifically affects compaction. There's
been some speculation that its purge code, but I don't think anyone's sat down
to comb through it yet to try and reproduce it.
> Compact and copy feature that resets changes
> --------------------------------------------
>
> Key: COUCHDB-1243
> URL: https://issues.apache.org/jira/browse/COUCHDB-1243
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Affects Versions: 1.0.1, 1.1
> Environment: Ubuntu, but not important
> Reporter: Henrik Hofmeister
> Labels: cleanup, compaction
> Attachments: dump_load.php
>
>
> After running db and view compaction on a 70K doc db with 6+ mio. changes -
> it takes up 0.8 GB. If copying the same documents to a new db (get and bulk
> insert) - the same date with 70K changes (only the inserts) takes up 40 mb.
> That is a huge difference. Has been verified on 2 db's that the difference is
> more than 65 times the size of data.
> A "Compact and copy" feature that copies only documents, and resets the
> changes for at db would be very nice to try and limit the disk usage a little
> bit. (Our current test environment takes up nearly 100 GB... )
> I've attached the dump load php script for your convenience.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
