| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On columnar storage |
| Date: | 2015-06-14 17:47:54 |
| Message-ID: | 11993.1434304074@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Another choice I considered was subquery_planner: in the spot where
> expand_inherited_tables() is called, add a new call to expand the RTEs
> that correspond to tables containing stores. But I had second thoughts
> because that function says "it's safe because it only adds baserels, not
> joins", and I'm adding joins.
I think that comment is only justifying why we don't need to redetermine
hasJoinRTEs/hasLateralRTEs/hasOuterJoins afterwards.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-06-14 17:54:27 | Re: On columnar storage |
| Previous Message | Bruce Momjian | 2015-06-14 17:41:45 | Re: 9.5 release notes |