From: Greg Stark <gsstark@mit.edu>
To: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Planner matching constants across tables in a join
Date: 05 Mar 2003 07:42:18 -0500
Message-ID: <87bs0q9e8l.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <200303051113.14320.dev@archonet.com>
References: <200303051113.14320.dev@archonet.com>
Richard Huxton <dev@archonet.com> writes:
> I know this has been covered on one of the lists in the past, but I'm damned
> if I can find the keywords to locate it.
>
> If I join two tables with a comparison to a constant on one, why can't the
> planner see that the comparison applies to both tables:
It sure does. Postgres does an impressive job of tracing equality clauses
around for just this purpose.
> SELECT a.id FROM a JOIN b ON a.id=b.id WHERE a.id=1;
>
> runs much slower than
>
> SELECT a.id FROM a JOIN b ON a.id=b.id WHERE a.id=1 AND b.id=1;
Really? They produce virtually the same plan for me.
Why do you think it'll run slower?
What query are you actually finding slow?
--
greg
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-performance@postgresql.org
Cc: gsstark@mit.edu, dev@archonet.com
Subject: Re: Planner matching constants across tables in a join
In-Reply-To: <87bs0q9e8l.fsf@stark.dyndns.tv>
References: <200303051113.14320.dev@archonet.com> <87bs0q9e8l.fsf@stark.dyndns.tv>
* 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