From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: a first step for the duplicate message-id dilemma
Date: Wed, 15 Mar 2017 22:57:26 -0300 [thread overview]
Message-ID: <20170316015728.29325-1-david@tethera.net> (raw)
These are mainly RFC because I'm not 100% sure about the performance
impact. It seems OK for me: about 3% slower indexing my 500 K
messages with about 35k duplicates. I didn't see a noticable increase
in database size (both cases it's 5.8G / 3.5G before/after notmuch
compact).
There are also tons of UI issues: for example in the test case here,
notmuch search subject:'"message 2"' will happily print
thread:0000000000000001 2001-01-05 [1/1] Notmuch Test Suite; message 1 (inbox unread)
I claim it's still an improvement over the current code, where that
second message is not findable by any terms unique to it.
next reply other threads:[~2017-03-16 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 1:57 David Bremner [this message]
2017-03-16 1:57 ` [RFC patch 1/2] test: add known broken test for duplicate message id David Bremner
2017-03-16 1:57 ` [RFC patch 2/2] lib: index message files with duplicate message-ids David Bremner
2017-03-16 18:22 ` Daniel Kahn Gillmor
2017-03-17 0:34 ` David Bremner
2017-03-17 16:44 ` Daniel Kahn Gillmor
2017-03-18 21:31 ` David Bremner
2017-03-22 17:29 ` Jani Nikula
2017-03-17 5:47 ` Mark Walters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170316015728.29325-1-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).