Re: PostgreSQL Advocacy, Thoughts and Comments

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Chris Travers" <chris(at)travelamericas(dot)com>
Cc: cnliou(at)so-net(dot)net(dot)tw, pgsql-general(at)postgresql(dot)org
Subject: Re: PostgreSQL Advocacy, Thoughts and Comments
Date: 2003-11-30 18:03:44
Message-ID: 24327.1070215424@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Chris Travers" <chris(at)travelamericas(dot)com> writes:
> The MySQL manual states that Joins perform better than subselects.

Very possibly true ... in MySQL. Since they have such an immature
subselect implementation (not even out of alpha apparently), it'd
not be surprising if they can't optimize subselects worth a damn yet.
Our planner has been hacked on repeatedly to do a good job with
subselects --- and I wouldn't want to imply that the process is done
yet.

One of the more amusing aspects of watching MySQL's response to the
"feature race" is how they invariably gloss over the difference between
having a minimal implementation of a feature, and having a feature that
is mature, complete, and efficient. Subselects are one example where
there's a lot of mileage yet to cover after you get to the point where
you can say "it works".

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2003-11-30 18:27:11 Re: PostgreSQL Advocacy, Thoughts and Comments
Previous Message Bruce Momjian 2003-11-30 17:44:48 Re: Making pg_dump cvs friendly