From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 8F1416DE226E for ; Tue, 21 Feb 2017 17:29:18 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.005 X-Spam-Level: X-Spam-Status: No, score=-0.005 tagged_above=-999 required=5 tests=[AWL=0.006, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HX9BFi9XzUH5 for ; Tue, 21 Feb 2017 17:29:16 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 512AB6DE2256 for ; Tue, 21 Feb 2017 17:29:16 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1cgLjR-00026S-1G; Tue, 21 Feb 2017 20:28:37 -0500 Received: (nullmailer pid 32338 invoked by uid 1000); Wed, 22 Feb 2017 01:29:12 -0000 From: David Bremner To: Andy Wills , notmuch@notmuchmail.org Subject: Re: bug report In-Reply-To: <20170221203517.GD13922@andy-x200> References: <20170221203517.GD13922@andy-x200> Date: Tue, 21 Feb 2017 21:29:12 -0400 Message-ID: <87poib3tef.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 01:29:18 -0000 Andy Wills writes: > > andy@andy-x200:~/work/talks/2017/icps$ notmuch new > Processed 230 total files in 7s (29 files/sec.). > Added 212 new messages to the database. Removed 85 messages. Detected 18 file renames. > Error: A Xapian exception occurred flushing database: Value in posting list too large. > > ...and it seems that, since I've been getting this error, new emails > are not reliably being found by, for example M-x notmuch in emacs. > Hi Andy; What version of notmuch is that? From the error message it sounds pre-2014. That particular code was rewritten in notmuch 0.19, so if my guess is correct it might be fixed by newer notmuch. d