Re: v4 of DB_RETRY_LOCK patches
On Sun, Jun 26 2016, David Bremner wrote: > This obsoletes > >id:1465043356-23420-2-git-send-email-da...@tethera.net > > I investigated adding a timeout (including talking a bit to Xapian > upstream about it), and thought about some runtime configuration > options, but for now I settled on a configure. Depending what > experiences people report, we would make the default disabled for the > next release. Looks good, tests pass (*) Tomi I.e. missing prerequisites: lock retry support SKIP all tests in T620-lock ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: v4 of DB_RETRY_LOCK patches
Thanks for getting this into shape, LGTM. FWIW, I have been running with DB_RETRY_LOCK for the past couple of months on a fairly large mail spool (500K emails), a high incoming volume and many tagging rules. So far it's been working great. No deadlocks, any delays waiting for locks are barely noticeable and it's so nice not having to deal with those annoying "already locked" failures. -- Istvan ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
v4 of DB_RETRY_LOCK patches
This obsoletes id:1465043356-23420-2-git-send-email-da...@tethera.net I investigated adding a timeout (including talking a bit to Xapian upstream about it), and thought about some runtime configuration options, but for now I settled on a configure. Depending what experiences people report, we would make the default disabled for the next release. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
