From: Alvaro Herrera <alvherre@commandprompt.com>
To: Warren Little <warren.little@meridiascapital.com>
Cc: Tomeh, Husam <htomeh@firstam.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: query optimization - mysql vs postgresql
Date: Fri, 19 May 2006 16:00:57 -0400
Message-ID: <20060519200057.GD4444@surnet.cl> (raw)
In-Reply-To: <1147970616.29462.20.camel@rearden1.reardeninc.local>
References: <CB0FB369FF86E248A884BCC002562BCB010C0E0B@pisgsna01sxch01.ana.firstamdata.com>
<1147970616.29462.20.camel@rearden1.reardeninc.local>
Warren Little wrote:
> Sorry,
> here are the attachments.
> Not sure about the statistics question, I have done a vacuum analyze on
> every table in the database.
The problem is that the planner is unable to appropiately order OUTER
JOINs in released versions. In 8.2 it can do some reordering, so it
would probably come up with a better plan. Without jumping to 8.2,
however, the best you could do is reorder the query yourself manually.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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-admin@postgresql.org
Cc: alvherre@commandprompt.com, warren.little@meridiascapital.com, htomeh@firstam.com
Subject: Re: query optimization - mysql vs postgresql
In-Reply-To: <20060519200057.GD4444@surnet.cl>
References: <CB0FB369FF86E248A884BCC002562BCB010C0E0B@pisgsna01sxch01.ana.firstamdata.com> <1147970616.29462.20.camel@rearden1.reardeninc.local> <20060519200057.GD4444@surnet.cl>
* 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