From: | Najm Hashmi <najm(at)mondo-live(dot)com> |
---|---|
To: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
Subject: | [sql]Joins |
Date: | 2000-11-10 15:59:28 |
Message-ID: | 3A0C1B60.9B4A97E5@mondo-live.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I am facing a dilemma at my work, I am using postgres first time. For
some reason, my co-workers think that in Postgres joins i.e.
simple joins of two or three tables are so bad that their cost is
exponential. They believe that postgres simply takes Cartesian product
of joining table in order to obtain desired tuples i.e. no optimization
is done.
I refused to believe so. I need your help to convince
them that it is okay to join tables --two or three tables :)-- so we can
eliminate redundancies from the database. I also want to know how
postgres optimizes a join query. Thank you very much your help.
Regards
Najm
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Boyanique | 2000-11-10 16:25:55 | SELECT FROM t1 WHERE id IN (SELECT id FROM t2 UNION SELECT id FROM t3) |
Previous Message | Sandis Jerics | 2000-11-10 11:55:18 | sorting the text values as integers |