| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: A fine point about OUTER JOIN semantics |
| Date: | 2000-09-04 21:35:40 |
| Message-ID: | 1690.968103340@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
>>>> In some cases, an outer join with WHERE restrictions reduces to
>>>> an inner join (so the qualification clauses can be consolidated).
>> I recall you having muttered something about that before, but I don't
>> see how it works. Can you give an example of an outer join that
>> reduces to an inner join?
> Hmm. This example is pretty silly, but afaik it reduces to an inner
> join:
> select i, j from t1 left join t2 using (i) where j is not null;
> (where t1 has column "i" and t2 has columns "i" and "j").
Well, I guess so, but I can't get excited about adding machinery to
detect cases like this ... are there any less-silly examples that make
a more compelling case for expending planner cycles to see if an outer
join can be reduced to an inner join?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris | 2000-09-04 22:51:34 | Re: OO inheritance implementation |
| Previous Message | Thomas Lockhart | 2000-09-04 18:25:28 | Re: A fine point about OUTER JOIN semantics |