X-Original-To: pgsql-sql@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 3897F475A8D for ; Fri, 7 Mar 2003 10:05:05 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h27F53x6000265; Fri, 7 Mar 2003 10:05:04 -0500 (EST) To: Andre Schubert Cc: Achilleus Mantzios , pgsql-sql@postgresql.org Subject: Re: Help on indexing timestamps In-reply-to: <20030307134702.135fa254.andre@km3.de> References: <20030307130223.5a58c132.andre@km3.de> <20030307134702.135fa254.andre@km3.de> Comments: In-reply-to Andre Schubert message dated "Fri, 07 Mar 2003 13:47:02 +0100" Date: Fri, 07 Mar 2003 10:05:03 -0500 Message-ID: <264.1047049503@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/195 X-Sequence-Number: 12235 Andre Schubert writes: > Yes if i use BETWEEN and type in the dates by hand the query takes about 200ms with explain analyze. > I think these is a good performance. > But if i use now() instead of manually typed dates the query take about 1400ms :( > I thought the somebody posted to this list, that now() is a function that is not cached, > and thatswhy does not work pretty well with indexes. Update to 7.3, and that problem will go away. regards, tom lane