Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g1IL4mE47224 for ; Mon, 18 Feb 2002 16:04:48 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g1IL4kS13745; Mon, 18 Feb 2002 16:04:46 -0500 (EST) To: "Kristian Eide" cc: pgsql-sql@postgresql.org Subject: Re: Why is my index not used In-reply-to: <00bd01c1b8ad$b9d03e90$6b97f181@speed> References: <00bd01c1b8ad$b9d03e90$6b97f181@speed> Comments: In-reply-to "Kristian Eide" message dated "Mon, 18 Feb 2002 19:54:42 +0100" Date: Mon, 18 Feb 2002 16:04:46 -0500 Message-ID: <13742.1014066286@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/282 X-Sequence-Number: 6705 "Kristian Eide" writes: > Why do postgre think it will get over 46k rows from this query? Not sure (and you didn't give the pg_statistic data that might tell us why). But it's no longer a very interesting question; we will not be fixing 7.1 optimizer bugs anymore. Please try it in 7.2 and see if you get better results. regards, tom lane