Subject: Re: PostgreSQL 12: Feature Highlights
References: <830415f7-78ec-ef7b-0f73-0e810ef87f91@postgresql.org>
 <f6225733-51c7-55a3-94fa-0a9f1d4a81eb@postgresql.org>
From: Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>
Message-ID: <eab862c2-033f-56a8-198f-18427f599096@lab.ntt.co.jp>
Date: Wed, 15 May 2019 11:31:32 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <f6225733-51c7-55a3-94fa-0a9f1d4a81eb@postgresql.org>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
To: "Jonathan S. Katz" <jkatz@postgresql.org>,
        pgsql-advocacy@lists.postgresql.org
Precedence: bulk

Hi Jonathan,

Thanks for the updated draft.

On 2019/05/15 11:03, Jonathan S. Katz wrote:
> Without further ado:
> 
> # Feature Highlights
> 
> 1. Indexing
> 
> - Improvements overall performance to standard (B-tree) indexes with
> writes as well as with bloat
> - REINDEX CONCURRENTLY
> - GiST indexes now support covering indexes (INCLUDE clause)
> - SP-GiST indexes now support K-NN queries
> - WAL overhead reduced on GiST, GIN, & SP-GiST index creation
> 
> 2. Partitioning Improvements
> 
> - Improved partition pruning, which improves performance on queries over
> tables with thousands of partitions that only need to use a few partitions
> - Improvements to COPY performance and ATTACH PARTITION
> - Allow foreign keys to reference partitioned tables

About the 1st item in "Partitioning Improvements", it's not just partition
pruning that's gotten better.  How about writing as:

 - Improved performance of processing tables with thousands of partitions
   for operations that only need to touch a small number of partitions

Per discussion upthread, that covers improvements to both partition
pruning and tuple routing.

Also, could the title "2. Partitioning Improvements" be trimmed down to
"2. Partitioning", to look like "1. Indexing" for consistency?

Thanks,
Amit