X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B81CFD1B1A5 for ; Wed, 9 Jun 2004 17:52:21 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 22151-04 for ; Wed, 9 Jun 2004 20:52:15 +0000 (GMT) Received: from server272.com (ns1.server272.com [64.14.68.49]) by svr1.postgresql.org (Postfix) with SMTP id B8059D1B16B for ; Wed, 9 Jun 2004 17:52:11 -0300 (ADT) Received: (qmail 2075 invoked from network); 9 Jun 2004 20:53:16 -0000 Received: from unknown (HELO pesky) (63.170.214.187) by server272.com with SMTP; 9 Jun 2004 20:53:16 -0000 Subject: Re: Index oddity From: ken To: Rod Taylor Cc: Postgresql Performance In-Reply-To: <1086811930.2539.90.camel@jester> References: <1086809460.32077.246.camel@pesky> <1086811930.2539.90.camel@jester> Content-Type: text/plain Message-Id: <1086814209.32077.252.camel@pesky> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 09 Jun 2004 13:50:09 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=HTML_MESSAGE, HTML_TAG_BALANCE_TABLE X-Spam-Level: X-Archive-Number: 200406/102 X-Sequence-Number: 7160 Thanks Rod, This setting has no effect however. If I set statistics to 1000, or even 0, (and then reanalyze the table) I see no change in the behaviour of the query plans. i.e. there is still the odd transtion in the plans at diagonalSize = 50. Ken On Wed, 2004-06-09 at 13:12, Rod Taylor wrote: > It seems to believe that the number of rows returned for the >49.999 > case will be 4 times the number for the >50 case. If that was true, then > the sequential scan would be correct. > > ALTER TABLE ALTER COLUMN diagonalsize SET STATISTICS 1000; > ANALZYE
; > > Send back EXPLAIN ANALYZE output for the >49.999 case. > > > The query plan for diagonalSize > 50.000 is ... > > > > Index Scan using nrgfeature_xys_index on nrgfeature f > > (cost=0.00..17395.79 rows=4618 width=220) > > Index Cond: ((upperrightx > 321264.236977215::double precision) AND > > (lowerleftx < 324046.799812083::double precision) AND (upperrighty > > > 123286.261898636::double precision) AND (lowerlefty < > > 124985.927450476::double precision) AND (diagonalsize > 50::double > > precision)) > > > > ... while for diagonalSize > 49.999 is ... > > > > Seq Scan on nrgfeature f (cost=0.00..31954.70 rows=18732 width=220) > > Filter: ((upperrightx > 321264.236977215::double precision) AND > > (lowerleftx < 324046.799812083::double precision) AND (upperrighty > > > 123286.261898636::double precision) AND (lowerlefty < > > 124985.927450476::double precision) AND (diagonalsize > 49.999::double > > precision)) > > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match >