| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP patch for parameterized inner paths |
| Date: | 2012-01-26 16:04:52 |
| Message-ID: | 5280.1327593892@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Is there a guard in here against joining a parameterized path to an
> intermediate relation when no SJ is involved? In other words, if
> we're joining a parameterized path on A to a path on B, then either
> the join to B should satisfy at least part of the parameterization
> needed by A, or there should be a special join with A and B on one
> side and a relation that satisfies at least part of the
> parameterization of A on the other.
There is no such guard. We could probably add one with not an
outrageous amount of expense, but I'm not clear on why you think it's
appropriate to limit the join ordering that way?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2012-01-26 16:10:26 | Re: information schema/aclexplode doesn't know about default privileges |
| Previous Message | Abhijit Menon-Sen | 2012-01-26 15:57:02 | Re: [PATCH] Fix float8 parsing of denormal values (on some platforms?) |