doc: update PG 11 release notes

Discussion: https://postgr.es/m/1f5b2e66-7ba8-98ec-c06a-aee9ff33f050@postgresql.org

Author: Jonathan S. Katz

Backpatch-through: 11
This commit is contained in:
Bruce Momjian 2018-10-05 17:20:24 -04:00
parent c87cb5f7a6
commit 6eb612fea9

View File

@ -6,7 +6,7 @@
<formalpara> <formalpara>
<title>Release date:</title> <title>Release date:</title>
<para>2018-??-?? (CURRENT AS OF 2018-07-30)</para> <para>2018-10-?? (CURRENT AS OF 2018-09-20)</para>
</formalpara> </formalpara>
<sect2> <sect2>
@ -22,7 +22,7 @@
<listitem> <listitem>
<para> <para>
Major improvements to partitioning: Improvements to partitioning functionality, including:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
@ -37,9 +37,8 @@
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Improved <command>SELECT</command> query performance due to Improved <command>SELECT</command> performance from enhanced partition
enhanced partition elimination during query processing and elimination strategies during query processing and execution
execution
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@ -48,22 +47,24 @@
KEY</literal>, indexes, and triggers on partitioned tables KEY</literal>, indexes, and triggers on partitioned tables
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Having a "default" partition for storing data that does not match any
of the remaining partitions
</para>
</listitem>
</itemizedlist> </itemizedlist>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Improvements to parallelism: Improvements to parallelism, including:
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<para> <para>
Parallelized hash joins B-tree indexes can now be built in parallel with
</para> <command>CREATE INDEX</command>
</listitem>
<listitem>
<para>
Parallelized <command>CREATE INDEX</command> for B-tree indexes
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@ -73,13 +74,22 @@
queries using <literal>UNION</literal> queries using <literal>UNION</literal>
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Performance improvements for parallelized hash joins and parallelized
sequential scans
</para>
</listitem>
</itemizedlist> </itemizedlist>
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
SQL stored procedures, with support for embedded transactions SQL stored procedures that support embedded transactions. Stored
procedures can be created with <link linkend="sql-createprocedure">
<command>CREATE PROCEDURE</command></link> and executed with
<link linkend="sql-call"><command>CALL</command></link>
</para> </para>
</listitem> </listitem>
@ -99,6 +109,13 @@
</para> </para>
</listitem> </listitem>
<listitem>
<para>
Covering indexes, which can be utilized using the
<literal>INCLUDE</literal> clause of <command>CREATE INDEX</command>
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Many other useful performance improvements, including making Many other useful performance improvements, including making
@ -179,10 +196,6 @@
would be dumped without such specifications if the database locale would be dumped without such specifications if the database locale
and encoding matched the old cluster's defaults. and encoding matched the old cluster's defaults.
</para> </para>
<para>
DID I GET EVERYTHING?
</para>
</listitem> </listitem>
<listitem> <listitem>
@ -597,8 +610,7 @@
The new command <link linkend="sql-alterindex"><command>ALTER The new command <link linkend="sql-alterindex"><command>ALTER
INDEX ATTACH PARTITION</command></link> allows indexes to be INDEX ATTACH PARTITION</command></link> allows indexes to be
attached to partitions. This does not behave as a global index attached to partitions. This does not behave as a global index
since the contents are private to each index. WARN WHEN USING since the contents are private to each index.
AN EXISTING INDEX?
</para> </para>
</listitem> </listitem>
@ -907,7 +919,7 @@ same commits as above
</para> </para>
<para> <para>
This reduces the likelihood of serialization conflicts. ACCURATE? This reduces the likelihood of serialization conflicts.
</para> </para>
</listitem> </listitem>
@ -1980,7 +1992,6 @@ same commits as above
<command>CALL</command>s or in nested PL/pgSQL DO and <command>CALL</command>s or in nested PL/pgSQL DO and
<command>CALL</command> blocks that only contain other PL/pgSQL <command>CALL</command> blocks that only contain other PL/pgSQL
<command>DO</command> and <command>CALL</command> blocks. <command>DO</command> and <command>CALL</command> blocks.
ACCURATE?
</para> </para>
</listitem> </listitem>
@ -2405,11 +2416,6 @@ same commits as above
when the <acronym>WAL</acronym> streaming method when the <acronym>WAL</acronym> streaming method
(<option>--wal-method=stream</option>) is used. (<option>--wal-method=stream</option>) is used.
</para> </para>
<para>
IS IT CLEAR FROM THE DOCS THAT THE REPLICATION SLOT IS NOT
TEMPORARY?
</para>
</listitem> </listitem>
<listitem> <listitem>
@ -2904,7 +2910,8 @@ same commits as above
</para> </para>
<para> <para>
This is useful for KNN-GiST searches. HOW? This is useful for KNN-GiST searches when looking for coordinates in
descending order.
</para> </para>
</listitem> </listitem>