X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 5DAD09F9F8F for ; Tue, 16 May 2006 12:27:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 89511-03 for ; Tue, 16 May 2006 12:26:54 -0300 (ADT) X-Greylist: delayed 11:52:56.559425 by SQLgrey- Received: from pdc.geeknet.com.au (unknown [210.9.9.216]) by postgresql.org (Postfix) with ESMTP id 7059A9F9C18 for ; Tue, 16 May 2006 12:26:51 -0300 (ADT) Received: from barney.geeknet.com.au ([192.168.61.101]) by pdc.geeknet.com.au with Microsoft SMTPSVC(6.0.3790.1830); Wed, 17 May 2006 01:26:48 +1000 Subject: Re: Can't get all search results From: John Hansen To: Bruce Momjian Cc: PostgreSQL www In-Reply-To: <200605161301.k4GD13Z26103@candle.pha.pa.us> References: <200605161301.k4GD13Z26103@candle.pha.pa.us> Content-Type: text/plain Date: Wed, 17 May 2006 01:26:48 +1000 Message-Id: <1147793208.7258.5.camel@barney.geeknet.com.au> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 May 2006 15:26:48.0721 (UTC) FILETIME=[260EF010:01C678FD] X-TM-AS-Product-Ver: SMEX-7.0.0.1345-3.52.1006-14448.003 X-TM-AS-Result: No--0.700000-8.000000-31 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/77 X-Sequence-Number: 10040 On Tue, 2006-05-16 at 09:01 -0400, Bruce Momjian wrote: > John Hansen wrote: > > On Wed, 2006-05-10 at 22:12 -0400, Bruce Momjian wrote: > > > I can't get all May 2006 search results to show up on: > > > > > > http://archives.postgresql.org/ > > > > > > If I search for "semaphore", I see only one entry for May 2006, while > > > this shows three emails with that title from the patches list for May > > > 7-8, 2006: > > > > > > http://archives.postgresql.org/pgsql-patches/2006-05/index.php > > > > > > > Aye, I'm aware of a problem with the sort by date functionality,... if > > you look closer you will see that they appear among the last few > > results. > > Oh, I definately see some strange date ordering on the last page. Can > you explain how something as simple as a date sort could not work 100%? Sure, the function that converts the webserver's response (the last_modified header returned by a HEAD request to be precise) to a unix timestamp, is by nature, somewhat uhmm,. unstable 'by nature' since there is no standard, an attempt has been made to cover the most common response formats. ... John