Eric Wong <e...@80x24.org> wrote: > Štěpán Němec <step...@smrk.net> wrote: > > Eric Wong wrote: > > > +Rerun deduplication on messages of with the given Message-ID or > > ^^^^^^^ > > not so fast :-P > > Thanks. Will s/of // when I commit when more awake. > Getting even more scatter-brained :x
OK, will probably push this out: --------8<-------- Subject: [PATCH] doc/extindex: document --dedupe switch We've had it since v1.7.0 when -extindex was introduced, but it was never documented outside of commit messages. --- Documentation/public-inbox-extindex.pod | 26 +++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-) diff --git a/Documentation/public-inbox-extindex.pod b/Documentation/public-inbox-extindex.pod index be4ea4de..b53e45ed 100644 --- a/Documentation/public-inbox-extindex.pod +++ b/Documentation/public-inbox-extindex.pod @@ -47,6 +47,20 @@ C<indexlevel> set to C<basic> and their respective Xapian public-inboxes where cross-posting is common, this allows significant space savings on Xapian indices. +=item --dedupe=MSGID + +=item --dedupe + +Rerun deduplication on messages with the given Message-ID or +all messages if no Message-ID is specified. Deduplication rules may +change and evolve over time, especially if filters are involved. + +C<--dedupe=MSGID> may be specified multiple times to deduplicate +multiple Message-IDs. + +Use this if you see C<W: BUG? $MSGID not deduplicated properly> +warnings from WWW logs. + =item --gc Perform garbage collection instead of indexing. Use this if @@ -61,10 +75,6 @@ used for in-place upgrades and bugfixes while read-only server processes are utilizing the index. Keep in mind this roughly doubles the size of the already-large Xapian database. -The extindex locks will be released roughly every 10s to -allow L<public-inbox-mda(1)> and L<public-inbox-watch(1)> -processes to write to the extindex. - =item --fast Used with C<--reindex>, it will only look for new and stale @@ -131,6 +141,14 @@ Default: none, uses C<publicinbox.indexBatchSize> Occasionally, public-inbox will update its schema version and require a full index by running this command. +=head1 LOCKING + +It is safe to use C<--dedupe>, C<--gc> and C<--reindex> while +other processes are writing to covered inboxes or extindex. +The extindex locks will be released roughly every 10s to +allow L<public-inbox-mda(1)> and L<public-inbox-watch(1)> +processes to write to the extindex. + =head1 CONTACT Feedback welcome via plain-text mail to L<mailto:meta@public-inbox.org>
