Re: PostgreSQL 12: Feature Highlights

Amit Langote <langote_amit_f8@lab.ntt.co.jp>

From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
To: Bruce Momjian <bruce@momjian.us>
Cc: David Rowley <david.rowley@2ndquadrant.com>, "Jonathan S. Katz" <jkatz@postgresql.org>, pgsql-advocacy@lists.postgresql.org
Date: 2019-05-21T00:47:54Z
Lists: 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




Commits

  1. doc: PG 12 relnotes, add mention of single-child optimization

  2. docs: split out sort-skip partition item in PG 12 release notes

  3. docs: update partition item in PG 12 release notes