| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: inner join removal |
| Date: | 2010-07-08 19:07:55 |
| Message-ID: | 4C36220B.5030403@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I think it might work out better if you ask "what
> additional conditions are needed in order to prove that this inner join
> can commute with this left join", and then work at being able to prove
> that. (It's entirely likely that the planner isn't currently gathering
> the right information for solving that problem.)
I also see this falling into a whole class of issues where the planner
could utilize the existance of FKs to plan queries better. That might
be a better first step.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-07-08 19:10:11 | Re: inner join removal |
| Previous Message | Tom Lane | 2010-07-08 19:05:20 | Re: inner join removal |