[PATCH] dump: make dump take Xapian write lock
David Bremner
david at tethera.net
Tue Jul 15 07:10:51 PDT 2014
Mark Walters <markwalters1009 at gmail.com> writes:
>
> Discussion with Olly on irc indicates that this is currently the best
> solution: in xapian trunk there may be better possibilities using
> snapshots but they need to make it to a release and propogate out to
> users before we can switch approach.
I agree that this seems to be the only feasible approach to make dump
atomic. I'm a little unsure about the benefits to the end user though.
Currently, the user has to check the return code of dump to ensure it
completed correctly. With this change, the user will still have to
check that dump did not error out when trying to acquire a write lock.
The following ticket
http://trac.xapian.org/ticket/275
suggests that if we wanted to a blocking open, we'd be on our own.
Did I miss something here about the benefits? I agree that failing
earlier is nicer, but is that it?
d
More information about the notmuch
mailing list