From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Olivier Hubaut <olivier(at)scmbb(dot)ulb(dot)ac(dot)be> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Why are these queries so different in time? |
Date: | 2005-07-29 15:42:48 |
Message-ID: | 42EA4E78.90305@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Olivier Hubaut wrote:
> Hi, I have a question about performance querying a 7.4 database. The
> orginal generated query was
>
> SELECT DISTINCT _compound0.object_id AS "ObjectId"
> FROM
(4 LEFT JOINS then a couple of WHERE conditions on 2 tables)
> This on take a huge time to perform, which may come to a timeout on the
> front-end application that uses the database.
> So, I decided to modify manually the query like this:
>
> SELECT DISTINCT _compound0.object_id AS "ObjectId"
> FROM
(Two lots of 2 x Left-joins, unioned together)
> This should give the same result set, but it's really faster than the
> previous one, more than one thousand time faster.
> Is there a reason for this huge difference of performance?
You're probably processing 1000 more rows in the first example. It's
probably running the LEFT JOIN across all the tables then restricting
the results in the WHERE. As it happens you're throwing away duplicates
with DISTINCT and/or UNION anyway, so you never get to see the results.
Try an EXPLAIN ANALYSE of the first example and see if the rows= parts
indicate very large numbers of rows being processed.
To make it faster I'd remove the LEFT JOINs, since your WHERE conditions
seem to rule out the NULL cases anyway.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | gherzig | 2005-07-29 15:59:28 | Re: calling EXECUTE on any exception |
Previous Message | Michael Fuhr | 2005-07-29 14:45:33 | Re: calling EXECUTE on any exception |