Skip site navigation (1) Skip section navigation (2)

Re: Outer join query plans and performance

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rich Doughty <rich(at)opusvl(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Outer join query plans and performance
Date: 2005-10-25 22:03:00
Message-ID: 29458.1130277780@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Rich Doughty <rich(at)opusvl(dot)com> writes:
> Tom Lane wrote:
>> The reason these are different is that the second case constrains only
>> the last-to-be-joined table, so the full cartesian product of t and h1
>> has to be formed.  If this wasn't what you had in mind, you might be
>> able to rearrange the order of the LEFT JOINs, but bear in mind that
>> in general, changing outer-join ordering changes the results.  (This
>> is why the planner won't fix it for you.)

> FWIW mysql 4.1 (and i'm no fan at all of mysql) completes both these queries
> in approximately 3 seconds.

Does mysql get the correct answer, though?  It's hard to see how they do
this fast unless they (a) are playing fast and loose with the semantics,
or (b) have very substantially more analysis logic for OUTER JOIN semantics
than we do.  Perhaps mysql 5.x is better about this sort of thing, but
for 4.x I'd definitely find theory (a) more plausible than (b).

The cases that would be interesting are those where rearranging the
outer join order actually does change the correct answer --- it may not
in this particular case, I haven't thought hard about it.  It seems
fairly likely to me that they are rearranging the join order here, and
I'm just wondering whether they have the logic needed to verify that
such a transformation is correct.

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2005-10-25 22:24:54
Subject: Re: Outer join query plans and performance
Previous:From: Chris MairDate: 2005-10-25 21:41:47
Subject: Re: insertion of bytea

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group