From: Richard Huxton <dev@archonet.com>
To: "Luiz Rafael Culik Guimaraes" <culikr@brturbo.com>,
	<pgsql-sql@postgresql.org>
Subject: Re: [SQL] query optimizer dont treat correctly OR
Date: Tue, 27 Apr 2004 16:35:39 +0100
User-Agent: KMail/1.5
Cc: <pgsql-general@postgresql.org>
References: <007101c42c66$c0bffb30$2b38fea9@luiz>
In-Reply-To: <007101c42c66$c0bffb30$2b38fea9@luiz>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200404271635.39024.dev@archonet.com>

On Tuesday 27 April 2004 15:48, Luiz Rafael Culik Guimaraes wrote:
> Hello folks
>
> See the command bellow. I use some thing simmilar about an decade on
> Oracle,
> Sybase, MSSQL, DB2, etc. But with  Postgresql , he generate an FULL TABLE
> SCAN,
> and consequenyly it take about 10 minutes to run (Very big table..)

> Why Post do this wrong julgment  with the initial command?
> Exist some thing that i can configure to to make postgres works correctly ?

You'll need to post the output of EXPLAIN ANALYSE for your query. This will 
show how many rows PG thinks it will get back compared to how many it 
actually gets back.

-- 
  Richard Huxton
  Archonet Ltd