On Mar 28, 2009, at 12:05 PM, Jeff Hinrichs - DM&T wrote:
On Sat, Mar 28, 2009 at 9:49 AM, Adam Kocoloski
<[email protected]> wrote:
On Mar 27, 2009, at 1:49 PM, Niket Patel wrote:
In current application we are seeing we are going to update
document every
few second because of autosave feature in application. So database
size will
grow too fast.
Is there any easy way to instruct couchdb to discard old
version(s) after
successful update. Though I don't have problem with compaction, this
requirement I'm seeing is document compaction.
Hi, individual document compaction is not possible today. Off the
top of
my head I think it would be pretty hard to implement that while
preserving
CouchDB's append-on-write semantics. Best,
Adam
How about rev stemming -- isn't this support to answer that very
question?
see test suite for info.. I don't know if there are docs on the wiki
yet.
Regards,
Jeff Hinrichs
Good point, Jeff. Revision stemming helps keep the size of the
frequently-updated document under control and slows the growth of the
database file. However, if you want to reclaim the disk space used by
the old revisions, you still need to compact the whole DB. Cheers,
Adam
