From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "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-21 00:47:54 |
Message-ID: | 1edcf5e3-fca8-14d6-6c03-b57921c21cb8@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
On 2019/05/18 0:36, Bruce Momjian wrote:
> On Fri, May 17, 2019 at 07:56:55PM +0900, Amit Langote wrote:
>> I agree that the current description captures at a high level the many
>> changes that made it possible. Although, a couple of commits listed with
>> this item don't have much to do with that description, AFAICT. Especially
>> 959d00e9d [1], which taught the planner to leverage the ordering imposed
>> on partitions by range partitioning. With that commit, getting ordered
>> output from partitioned tables is now much quicker, especially with a
>> LIMIT clause. You can tell that it sounds clearly unrelated to the
>> description we have now, which is "processing thousands of partitions is
>
> Yes, it does. I added this text and moved the commit item:
>
> Avoid sorting when partitions are already being scanned in the
> necessary order (David Rowley)
Thank you Bruce.
Regards,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2019-05-21 14:55:09 | Re: PostgreSQL 12: Feature Highlights |
Previous Message | David Rowley | 2019-05-18 14:26:48 | Re: PostgreSQL 12: Feature Highlights |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-21 00:48:15 | Re: PG 12 draft release notes |
Previous Message | David Rowley | 2019-05-21 00:43:03 | Re: Parallel Append subplan order instability on aye-aye |