From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, pgsql-advocacy(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL 12: Feature Highlights |
Date: | 2019-05-22 00:23:13 |
Message-ID: | 82a518da-22e5-269f-c350-7caa1d948165@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On 2019/05/21 23:55, Bruce Momjian wrote:
> On Sun, May 19, 2019 at 02:26:48AM +1200, David Rowley wrote:
>> Thanks, typing that up. I think it lacks a bit detail about what's
>> actually changed. The change is fairly evident and people can see
>> when it takes effect when they look at EXPLAIN and see that the
>> Append/MergeAppend node is missing. Also, an Append/MergeAppend may
>> exist for inheritance tables and an Append can exist for a simple
>> UNION ALL. Both of those cases can have subplans removed to leave only
>> a single subplan, to which the additional parallel paths will be
>> considered.
>
> This brings up a few points. First, it seems the change affects
> partitioned tables and UNION ALL, which means it probably needs to be
> listed in two sections.
How about putting this only in E.1.3.1.3. Optimizer?
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2019-05-22 00:33:10 | Re: PostgreSQL 12: Feature Highlights |
Previous Message | Bruce Momjian | 2019-05-21 14:55:09 | Re: PostgreSQL 12: Feature Highlights |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2019-05-22 00:33:10 | Re: PostgreSQL 12: Feature Highlights |
Previous Message | Ian Barwick | 2019-05-22 00:19:53 | Re: PG 12 draft release notes |