Re: PostgreSQL 12: Feature Highlights
От | Amit Langote |
---|---|
Тема | Re: PostgreSQL 12: Feature Highlights |
Дата | |
Msg-id | eab862c2-033f-56a8-198f-18427f599096@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: PostgreSQL 12: Feature Highlights ("Jonathan S. Katz" <jkatz@postgresql.org>) |
Ответы |
Re: PostgreSQL 12: Feature Highlights
Re: PostgreSQL 12: Feature Highlights |
Список | pgsql-advocacy |
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
В списке pgsql-advocacy по дате отправления: