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 9FAE5D1D282 for ; Fri, 9 Apr 2004 02:26:56 -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 53271-08 for ; Fri, 9 Apr 2004 02:26:54 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8C01DD1C9DA for ; Fri, 9 Apr 2004 02:26:54 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i395QqlA021350; Fri, 9 Apr 2004 01:26:52 -0400 (EDT) To: Mark Lubratt Cc: pgsql-performance@postgresql.org, josh@agliodbs.com Subject: Re: tsearch query plan In-reply-to: References: <200404081633.40388.josh@agliodbs.com> Comments: In-reply-to Mark Lubratt message dated "Thu, 08 Apr 2004 22:28:37 -0500" Date: Fri, 09 Apr 2004 01:26:51 -0400 Message-ID: <21349.1081488411@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/117 X-Sequence-Number: 6417 Mark Lubratt writes: > I guess I was looking more at the cost estimate and not so much at the > rows estimate. I agree that the row estimate wasn't too bad. But the > cost estimate seems way out of line. The cost estimates are not even in the same units as the actual runtime. Cost is in an arbitrary scale in which 1 unit = 1 sequential disk block fetch. It is unknown what this might equate to on your machine ... but it's quite unlikely that it's 1.0 millisecond. The thing to look at when considering EXPLAIN results is whether the ratios of different cost estimates are proportional to the actual runtimes. regards, tom lane