incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Joseph Davis (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1243) Compact and copy feature that resets changes
Date Tue, 09 Aug 2011 01:16:27 GMT


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

> Compact and copy feature that resets changes
> --------------------------------------------
>                 Key: COUCHDB-1243
>                 URL:
>             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:


View raw message