From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | Dimitri <dimitrik(dot)fr(at)gmail(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Any better plan for this query?.. |
Date: | 2009-05-07 11:58:50 |
Message-ID: | 87iqkdunt1.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> We already know that MySQL favors nested loop joins
From what I read I thought that was the *only* type of join MySQL supports.
The big picture view here is that whether we run a short query in half a
millisecond versus two milliseconds is usually not really important. It could
matter if you're concerned with how many transactions/s you can run in a busy
server -- but that's not exactly the same thing and you should really measure
that in that case.
It would be nice if we were in the same ballpark as MySQL but we would only be
interesting in such optimizations if they don't come at the expense of
scalability under more complex workloads.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-05-07 12:21:32 | Re: Any better plan for this query?.. |
Previous Message | Merlin Moncure | 2009-05-07 11:34:55 | Re: Any better plan for this query?.. |