From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: blog post on gnus, dovecot, and lucene
Date: Thu, 09 Oct 2014 16:23:02 +0800 [thread overview]
Message-ID: <87tx3dtzx5.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3vbnthksh.fsf@neo.luffy.cx>
Vincent Bernat <bernat@luffy.cx> writes:
> ❦ 8 octobre 2014 22:15 +0800, Eric Abrahamsen <eric@ericabrahamsen.net> :
>
>>> I didn't notice that. I added that to my dovecot.conf:
>>>
>>> plugin {
>>> fts = lucene
>>> fts_lucene = whitespace_chars=@.
>>> }
>>>
>>> And the search became faster. However, I usually don't use FTS (only
>>> search on recipient or title). If I check right now, I notice that the
>>> indexes are not up-to-date. So, you may be right.
>>
>> But it's pretty interesting that that did something -- I wasn't sure
>> that calling dovecot as a process would even invoke the configuration
>> files at all. But you don't think the indexes were updated, huh?
>>
>> It might be worth amending the blog post at some point. I've asked about
>> this stuff on the dovecot mailing list, but no one seemed to know.
>
> I have done a doveadm fts rescan to get those indexes updated. So, maybe
> the solution could be a cronjob?
Right, that should work fine. At that point, though, I'm inclined just
to have dovecot run as a daemon...
next prev parent reply other threads:[~2014-10-09 8:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 5:43 Eric Abrahamsen
2014-10-07 5:51 ` Igor Sosa Mayor
2014-10-07 11:14 ` Feng Shu
2014-10-07 11:59 ` Rasmus
2014-10-07 10:09 ` Vincent Bernat
2014-10-07 16:30 ` Eric Abrahamsen
2014-10-08 5:12 ` Vincent Bernat
2014-10-08 14:15 ` Eric Abrahamsen
2014-10-09 5:30 ` Vincent Bernat
2014-10-09 8:23 ` Eric Abrahamsen [this message]
2014-10-09 8:30 ` Rainer M Krug
[not found] ` <m2oatos5yt.fsf@krugs.de>
2014-10-07 16:47 ` Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tx3dtzx5.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).