DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=sender:from:to:subject:in-reply-to:references:date:message-id
	:mime-version:content-type;
	b=Nt59rmMbGM3/M05OTxowx2AdIIu35bSc4zBew3iFdjWtHdK1w8Q3sQp3kq22uX2U/x
	I3ssd1dSRHvLyv3g+AtOJQr421QN5Ua/8zOajQyGxkFxuEi67IvTv8NkGRJXTwtcfrq7
	cl8bqQpm0uuT0nkugjyoS3j6tDGfVvhm8jVSE=
Sender: Jed Brown <five9a2@gmail.com>
From: Jed Brown <jed@59A2.org>
To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org
In-Reply-To: <874oon4pgv.fsf@yoom.home.cworth.org>
References: <87fx87u3no.fsf@59A2.org> <874oon4pgv.fsf@yoom.home.cworth.org>
Date: Sat, 21 Nov 2009 21:48:19 +0100
Message-ID: <87d43btxik.fsf@59A2.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [notmuch] Asynchronous tagging
Precedence: list

On Sat, 21 Nov 2009 21:01:20 +0100, Carl Worth <cworth@cworth.org> wrote:
> Yes, this is a known bug in Xapian (it rewrites all of the indexed terms
> for the email message even though you're just trying to add/remove one
> term). The Xapian ticket for this is here:
> 
> 	replace_document should make minimal changes to database file
> 	http://trac.xapian.org/ticket/250

This bug report is concerned that it could require an API change, it
sounds like you think this is unnecessary.  Thanks for the detailed
explanation.

> Chris Wilson just contributed a patch to enable read-only usage of
> notmuch while another notmuch process holds the write lock.

I'm running it.

> Does offlineimap use tmp while it's delivering message and then move
> things to new? If so, then maybe all we need to do to fix notmuch to not
> look into tmp directories?

Yes, that's how maildir is supposed to work.  Deliver to tmp, hard link
from new, then unlink in tmp.  The client should never look in tmp.
Should be very quick to fix in notmuch.

Jed