Re: More grist for the PostgreSQL vs MySQL mill - Mailing list pgsql-general

From John Meyer
Subject Re: More grist for the PostgreSQL vs MySQL mill
Date
Msg-id 45B2E76D.6070505@gmail.com
Whole thread Raw
In response to Re: More grist for the PostgreSQL vs MySQL mill  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: More grist for the PostgreSQL vs MySQL mill  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: More grist for the PostgreSQL vs MySQL mill  ("Chad Wagner" <chad.wagner@gmail.com>)
Re: More grist for the PostgreSQL vs MySQL mill  ("Michael Nolan" <htfoot@gmail.com>)
List pgsql-general
What I think bothers me is this whole concept that if PostgreSQL is to
flourish, MySQL has to be beaten down.  Folks, both products are free,
both can be used in the same shop (maybe not on the same computer if
your running them in production).  Putting down MySQL will not make
PostgreSQL any better, or vice versa.

Tom Lane wrote:
> "Michael Nolan" <htfoot@gmail.com> writes:
>> select count(*) from memmast where memid in (select plr_rated_memid from
>> tnmt_plr where plr_eventid in ('200607163681');
>
>> This query takes about a second on PostgreSQL but takes OVER SEVEN MINUTES
>> on MySQL!
>
> Yeah, and we probably would have sucked about as badly before 7.4 or so.
> There's a long way from "having subselects" to being able to optimize
> them decently.  AFAIK mysql is still at the "we've got subselects!"
> stage ...
>
>             regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: More grist for the PostgreSQL vs MySQL mill
Next
From: "Joshua D. Drake"
Date:
Subject: Re: More grist for the PostgreSQL vs MySQL mill