Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B43EE650EFE for ; Thu, 26 Jun 2008 19:35:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 70706-01 for ; Thu, 26 Jun 2008 19:35:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id AC01D650EF8 for ; Thu, 26 Jun 2008 19:35:29 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id m5QMZT109827; Thu, 26 Jun 2008 18:35:29 -0400 (EDT) From: Bruce Momjian Message-Id: <200806262235.m5QMZT109827@momjian.us> Subject: Re: No search results for "now" In-Reply-To: <54b33ccd0805070152r5f2f9fdek7d443145dd4e5b39@mail.gmail.com> To: Marti Raudsepp Date: Thu, 26 Jun 2008 18:35:29 -0400 (EDT) CC: pgsql-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: 200806/185 X-Sequence-Number: 15412 Marti Raudsepp wrote: > Hi, > > Someone pointed out in #postgresql that a search for "now" apparently > gives no results, even though PostgreSQL has a now() function: > http://search.postgresql.org/search?u=%2Fdocs%2F8.3%2Fstatic%2F&q=now > > Probably needs to be fixed. I can confirm this bug. Anyone know the cause? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +