X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9DB24D1BAAD for ; Thu, 8 Apr 2004 20:33:27 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 60163-05 for ; Thu, 8 Apr 2004 20:33:28 -0300 (ADT) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 69855D1B49F for ; Thu, 8 Apr 2004 20:33:25 -0300 (ADT) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4801472; Thu, 08 Apr 2004 16:34:48 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Mark Lubratt , pgsql-performance@postgresql.org Subject: Re: tsearch query plan Date: Thu, 8 Apr 2004 16:33:40 -0700 User-Agent: KMail/1.5.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404081633.40388.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/115 X-Sequence-Number: 6415 Mark, > I've got one question about query planning. Is it understandable to > have the query plan estimation be off by a couple of orders of > magnitude? Or, is it the fact that the cost estimation is small to > begin with that the error between the actual and the estimated is > "normal"? Well, your example is not "a couple orders of magnitude". 6 vs. 32 is actually pretty good accuracy. Now, 6 vs 192 would potentially be a problem, let alone 32 vs 13,471. -- -Josh Berkus Aglio Database Solutions San Francisco