From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Stefan Schwarzer <stefan(dot)schwarzer(at)grid(dot)unep(dot)ch> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Subqueries or Joins? Problems with multiple table query |
Date: | 2010-02-23 13:28:24 |
Message-ID: | bddc86151002230528v5e9da7b9jc0f49de715307c07@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 23 February 2010 13:23, Stefan Schwarzer
<stefan(dot)schwarzer(at)grid(dot)unep(dot)ch> wrote:
>> Select countries.name, basel.year, basel.value, cites.year, cites.value
>> From countries
>> Left Join basel on basel.id_country = countries.id_country and
>> basel.value=1
>> Left Join cites on cites.id_country = countries.id_country and
>> cites.value=1
>
> I would have thought so, but the query turns forever.
How many rows in each of your tables, and what indexes do you have?
You may also wish to review Andreas' suggestions as they propose a
more sensible table structure rather than having a table for each
convention.
You may also be interested in the tablefunc contrib module to help
present your data in the format you require rather than having a join
for each convention:
http://www.postgresql.org/docs/8.4/static/tablefunc.html
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2010-02-23 13:32:01 | Re: Alternative to UPDATE (As COPY to INSERT) |
Previous Message | Stefan Schwarzer | 2010-02-23 13:23:25 | Re: Subqueries or Joins? Problems with multiple table query |