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 3AF04D1B8CB for ; Thu, 4 Sep 2003 15:25:07 +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 47853-02 for ; Thu, 4 Sep 2003 12:24:56 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id 705C7D1B89A for ; Thu, 4 Sep 2003 12:24:56 -0300 (ADT) Received: from news.hub.org (host-64-117-224-194.altec1.com [64.117.224.194] (may be forged)) by news.hub.org (8.12.9/8.12.9) with ESMTP id h84FOuDf081734 for ; Thu, 4 Sep 2003 15:24:56 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h84F521X075771 for pgsql-performance@postgresql.org; Thu, 4 Sep 2003 15:05:02 GMT From: "Relaxin" X-Newsgroups: comp.databases.postgresql.performance Subject: Re: SELECT's take a long time compared to other DBMS Date: Thu, 4 Sep 2003 08:05:15 -0700 Organization: Hub.Org Networking Services Lines: 39 Message-ID: References: <3F5753B9.F4A5A63F@nsd.ca> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/62 X-Sequence-Number: 3428 The table has been Vacuumed and seq_scan is turned on. "Jean-Luc Lachance" wrote in message news:3F5753B9.F4A5A63F@nsd.ca... > You forgot that the original poster's query was: > SELECT * from > > This should require a simple table scan. NO need for stats. > Either the table has not been properly vacuumed or he's got seq_scan > off... > > JLL > > > Nick Fankhauser wrote: > > > > > 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 > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 2: you can get off all lists at once with the unregister command > > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings >