X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 09C5130EEFC for ; Mon, 16 Jun 2003 23:46:38 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 67568-07 for ; Mon, 16 Jun 2003 20:46:27 -0300 (ADT) Received: from email03.aon.at (WARSL402PIP6.highway.telekom.at [195.3.96.93]) by svr1.postgresql.org (Postfix) with SMTP id E389530EFBA for ; Mon, 16 Jun 2003 20:46:26 -0300 (ADT) Received: (qmail 393310 invoked from network); 16 Jun 2003 23:46:26 -0000 Received: from m149p004.dipool.highway.telekom.at (HELO cantor) ([62.46.8.132]) (envelope-sender ) by qmail3rs.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 16 Jun 2003 23:46:26 -0000 From: Manfred Koizar To: Ernest E Vogelsinger Cc: pgsql-performance@postgresql.org, pgsql-general@postgresql.org Subject: Re: Interesting incosistent query timing Date: Tue, 17 Jun 2003 01:45:58 +0200 Message-ID: References: <5.1.1.6.2.20030617003809.02deaa78@mail.vogelsinger.at> In-Reply-To: <5.1.1.6.2.20030617003809.02deaa78@mail.vogelsinger.at> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200306/964 X-Sequence-Number: 43894 On Tue, 17 Jun 2003 00:46:54 +0200, Ernest E Vogelsinger wrote: >For the first time run it executes in 1.5 - 2 seconds. From the second >time, only 10 msec are needed for the same result I'd call it inconsistent, if it were the other way round :-) I guess you are seeing the effects of disk caching. Watch the drive LED during the first run ... Servus Manfred