From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ingram, Bryan <BIngram@sixtyfootspider.com>
Cc: 'pgsql-sql@postgresql.org' <pgsql-sql@postgresql.org>
Subject: Re: Why is this doing a seq scan?
Date: Fri, 17 Nov 2000 16:39:53 -0500
Message-ID: <14140.974497193@sss.pgh.pa.us> (raw)
In-Reply-To: <01CCE949D2717845BA2E573DC081167E052FB0@BKMAIL.sfsinternal.com>
References: <01CCE949D2717845BA2E573DC081167E052FB0@BKMAIL.sfsinternal.com>
"Ingram, Bryan" <BIngram@sixtyfootspider.com> writes:
>> Also it would be useful to see the full declarations of the tables
>> and their indexes; I'm wondering what datatype the zip columns are,
>> for example.
> Table = atms
> | zip | text |
> Table = zips
> | zip | varchar() |
Ah, there's your problem --- the planner is not very smart about
optimizing cross-datatype comparisons. Make these columns both text,
or both varchar, and I'll bet you get a more intelligent plan.
Current sources (7.1-to-be) are a little smarter than 7.0 about
cross-data-type joins, but they still don't get this case right.
I have a TODO item about that, but I dunno if it'll get done before
7.1 ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, BIngram@sixtyfootspider.com
Subject: Re: Why is this doing a seq scan?
In-Reply-To: <14140.974497193@sss.pgh.pa.us>
References: <01CCE949D2717845BA2E573DC081167E052FB0@BKMAIL.sfsinternal.com> <14140.974497193@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox