Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 3D2962E00D3 for ; Tue, 11 Mar 2008 21:56:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 83642-09 for ; Tue, 11 Mar 2008 21:56:33 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 870172E00E1 for ; Tue, 11 Mar 2008 21:56:41 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id m2C0ufJ19655; Tue, 11 Mar 2008 20:56:41 -0400 (EDT) From: Bruce Momjian Message-Id: <200803120056.m2C0ufJ19655@momjian.us> Subject: Re: Email not searchable in our archives In-Reply-To: <20080312005124.GD6737@alvh.no-ip.org> To: Alvaro Herrera Date: Tue, 11 Mar 2008 20:56:41 -0400 (EDT) CC: PostgreSQL www X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/233 X-Sequence-Number: 14352 Alvaro Herrera wrote: > Bruce Momjian wrote: > > Alvaro Herrera wrote: > > > > I can fix the problem by providing URLs with message ids. Would that > > > help? You can find out the Message-Id trivially from the original > > > email, and the URL would take you to the main message page complete with > > > thread links and all. > > > > I have been pasting the email subject line into the search and usually > > it is the first hit (when search works). > > I am not saying we should continue to have a broken search -- I only say > that I can fix your particular use case. If you're not interested in it > I can easily push the issue down in my TODO list. I don't feel it is right that you have to push up a TODO item just because the search is broken. -- Bruce Momjian http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +