From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 18:24:02 |
Message-ID: | 20150614182402.GK133018@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Tom Lane wrote:
> >> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> >>> Won't this cause issues to MergeAppend optimizations?
>
> >> Like what?
>
> > Well, as I understand, MergeAppend needs to know the sort order of the
> > child node, right? But that's available only on the relation RTE, not
> > on the colstore-join RTE.
>
> Uh, what? Sort order is a property of a path, not an RTE.
Evidently need to do more digging .. but that makes plenty of sense.
> And we have always understood which join types preserve sort order.
That's obvious now that you say it.
> You misunderstood the thrust of my comment, which basically is that
> I doubt anyone will think that rejecting that combination is an
> acceptable implementation restriction. It might be all right if it
> doesn't work very well in v0, but not if the implementation is designed
> so that it can never be fixed.
Gotcha.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-06-14 18:37:05 | The real reason why TAP testing isn't ready for prime time |
Previous Message | Tom Lane | 2015-06-14 18:18:55 | Re: On columnar storage |