X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8B1A6D1B8C5 for ; Thu, 4 Sep 2003 04:45:18 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 96634-01 for ; Thu, 4 Sep 2003 01:44:48 -0300 (ADT) Received: from grebe.mail.pas.earthlink.net (grebe.mail.pas.earthlink.net [207.217.120.46]) by svr1.postgresql.org (Postfix) with ESMTP id 64212D1B8B3 for ; Thu, 4 Sep 2003 01:44:47 -0300 (ADT) Received: from 0-1pool116-178.nas15.indianapolis1.in.us.da.qwest.net ([65.128.116.178] helo=nick) by grebe.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19ulzC-0002v1-00 for pgsql-performance@postgresql.org; Wed, 03 Sep 2003 21:44:46 -0700 Reply-To: From: "Nick Fankhauser" To: Subject: Re: SELECT's take a long time compared to other DBMS Date: Wed, 3 Sep 2003 23:43:45 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/49 X-Sequence-Number: 3415 > Yes I Analyze also, but there was no need to because it was a fresh brand > new database. This apparently wasn't the source of problem since he did an analyze anyway, but my impression was that a fresh brand new database is exactly the situation where an analyze is needed- ie: a batch of data has just been loaded and stats haven't been collected yet. Am I mistaken? -Nick