CouchDB only rebuilds view indexes when two purge operations happen WITHOUT a view index update in between.
If you can guarantee that you have a vie index update after each purge, using purge for removing tombstones is a viable solution. I’m short on time right now, but happy to write up how it all works tomorrow. Best Jan -- > On 31 May 2016, at 17:26, Dale Harvey <[email protected]> wrote: > > Does mango share the same disadvantages as map reduce with indexes having > to be rebuilt on purge? In PouchDB it currently does however we are looking > to change the pouchdb-find implementation so that purge has no negative > effect on the query performance, at which point we will implement and be > happy pointing users towards using purge (with the caveats about their > affect on replication). > > With PouchDB we have to be very aware about keeping local disk size to a > minimum and recommending to users that they replicate to new databases in > order to save disk size is not user friendly imo, so we are definitely > interested in looking at ways to improve disk space usage. Moving purge > away from 'avoid this' territory is one way. > > On 31 May 2016 at 16:12, Stefan Klein <[email protected]> wrote: > >> Hi, >> >> 2016-05-31 17:00 GMT+02:00 david rene comba lareu < >> [email protected]>: >> >>> HI, >>> >> >> [ ... ] >> >> >>> >>> 1) when you delete a document, is supposed that revisions are only >>> deleted after the cleanup, but the tombstones are still there, and it >>> increase the amount of size exponentially. i found this post about it: >>> >>> >> http://eclipsesource.com/blogs/2015/04/20/how-to-finally-delete-documents-in-couchdb/ >>> with a sort of solution, that i find tricky and insecure. i don't want >>> be manipulating live DB's on live servers. any other option? >>> >> >> I haven't double checked, but if i remember correctly purging 2 documents >> will cause all views to be re-created. >> Purge is really not to be meant for normal operation. >> >> So the replication of non deleted documents to a new DB is - to my >> knowledge - the only option. >> >> Do you have a proxy in front of your couchdb? >> If so, you do not even need to shut down and copy DB files, but you could >> simply point the proxy to the new DB. >> Remember to refresh the views before switching DBs. >> >> -- >> Stefan >> -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/
