Date: Mon, 30 Oct 2006 16:49:57 +0100
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Mattias Kregert <mattias@kregert.se>
Cc: pgsql-performance@postgresql.org
Subject: Re: Strange plan in pg 8.1.0
Message-ID: <20061030154957.GA7834@uio.no>
Mail-Followup-To: Mattias Kregert <mattias@kregert.se>,
	pgsql-performance@postgresql.org
References: <200610301205.08087.mattias@kregert.se>
	<20061030122733.GA6357@uio.no>
	<003301c6fc2f$57e2c660$09000a0a@kregert.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <003301c6fc2f$57e2c660$09000a0a@kregert.se>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Mon, Oct 30, 2006 at 03:26:09PM +0100, Mattias Kregert wrote:
> On the left side it is text, and on the right side it is varchar(10).
> Casting left side to varchar(10) does not help, in fact it makes things 
> even worse: The cast to ::text vanishes in a puff of logic, but the plan 
> gets bigger and even slower (20-25 seconds).

Casting definitely won't help it any; it was more a question of having the
types in the _tables_ be the same.

Anyhow, this might be a red herring; others might have something more
intelligent to say in this matter.

By the way, does it use an index scan if you turn off sequential scans
(set enable_seqscan = false)?

/* Steinar */
-- 
Homepage: http://www.sesse.net/