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 556D06DE1500 for ; Sat, 1 Jun 2019 07:13:19 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.044 X-Spam-Level: X-Spam-Status: No, score=-0.044 tagged_above=-999 required=5 tests=[AWL=-0.043, SPF_PASS=-0.001] 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 21y5yAXTx-o2 for ; Sat, 1 Jun 2019 07:13:18 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 525F46DE14FE for ; Sat, 1 Jun 2019 07:13:18 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1hX4l2-0005w3-DW; Sat, 01 Jun 2019 10:13:16 -0400 Received: (nullmailer pid 19218 invoked by uid 1000); Sat, 01 Jun 2019 14:13:25 -0000 From: David Bremner To: Daniel Kahn Gillmor , Notmuch Mail Subject: Re: feature request: caching message arrival time In-Reply-To: <8736kuhtky.fsf@fifthhorseman.net> References: <8736kuhtky.fsf@fifthhorseman.net> Date: Sat, 01 Jun 2019 11:13:25 -0300 Message-ID: <874l59qtq2.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 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: Sat, 01 Jun 2019 14:13:19 -0000 Daniel Kahn Gillmor writes: > * i don't think we have a way to search properties by range (e.g. the > way that we can search date ranges). i don't need that feature for > my use case, but maybe someone will come up with a use case that > wants it? is there a way to store the datestamp in a way that it can > be scanned the way that "date" can? or do we already have this and > i'm just unaware? you'd need to use a value slot to get (native Xapian) range searches. To quote the xapian docs For performance it is important to keep the amount of data stored in the values to a minimum, since the values for a large number of documents may be read during the search - the more data that has to be read, the slower the search will be. So it's definitely something that would need to be profiled. Probably the patches that added lastmod: are a good example for someone wanting to investigate this.