Hi, This is the most common mistake made with CouchDB, that it provides (or could provide) a full history of document changes.
Compaction is essential, it's the only time that the b+tree's are rebalanced and obsolete version of b+tree nodes are removed from disk. If the old revisions of your documents really matter, make new documents instead of updating them, and use some scheme of your choice to group them (you could use a view on some property common to all revisions of the same logical document). B. > On 27 Apr 2020, at 17:10, Andrea Brancatelli > <[email protected]> wrote: > > Let's say I'd like to keep the whole revision history for documents in a > specific database (but maybe drop old views, if it's possible). > > What compaction setting would do that overriding the more-reasonable > default we usually have? > > -- > > Andrea Brancatelli
