postgrespro.git / summary / log / commit / refs
commit 545a065880be8ccddfb116a0915bfdac0cd41902
Author: Bruce Momjian <bruce@momjian.us>
Date: Thu May 07 13:00:24 2020 +0000
doc: PG 13 relnotes: adjust partition items and attributions
This merges three partition publication items into two.
doc/src/sgml/release-13.sgml | 33 ++++++++++-----------------------
1 file changed, 10 insertions(+), 23 deletions(-)
diff --git a/doc/src/sgml/release-13.sgml b/doc/src/sgml/release-13.sgml
index 2ec8bb2748..1e46248491 100644
--- a/doc/src/sgml/release-13.sgml
+++ b/doc/src/sgml/release-13.sgml
@@ -254,7 +254,7 @@ Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
-->
<para>
-Improve cases where pruning of partitions can happen (Amit Langote, Yuzuko Hosoya, Álvaro Herrera)
+Improve cases where pruning of partitions can happen (Yuzuko Hosoya, Amit Langote, Álvaro Herrera)
</para>
</listitem>
@@ -268,7 +268,7 @@ Author: Tom Lane <tgl@sss.pgh.pa.us>
-->
<para>
-Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita, Amit Langote)
+Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita, Amit Langote, Tom Lane)
</para>
</listitem>
@@ -289,30 +289,21 @@ These triggers cannot change which partition is the destination.
</listitem>
-<listitem>
-<!--
-Author: Peter Eisentraut <peter@eisentraut.org>
-2020-04-06 [f1ac27bfd] Add logical replication support to replicate into partit
--->
-
-<para>
-Allow logical replication to replicate partitioned tables (Amit Langote)
-</para>
-
-</listitem>
-
<listitem>
<!--
Author: Peter Eisentraut <peter@eisentraut.org>
2020-03-10 [17b9e7f9f] Support adding partitioned tables to publication
+Author: Peter Eisentraut <peter@eisentraut.org>
+2020-04-08 [83fd4532a] Allow publishing partition changes via ancestors
-->
<para>
-Allow partitioned tables to be added to replicated publications (Amit Langote)
+Allow partitioned tables to be logically replicated via publications (Amit Langote)
</para>
<para>
-Partition additions/removals are replicated as well. Previously, partitions had to be replicated individually. HOW IS THIS DIFFERENT FROM THE ITEM ABOVE?
+Previously, partitions had to be replicated individually. Now partitioned tables can be published explicitly causing all partitions to be automatically published. Addition/removal of partitions from
+partitioned tables are automatically added/removed from publications. The CREATE PUBLICATION option publish_via_partition_root controls whether partitioned tables are published as themselves or their ancestors.
</para>
</listitem>
@@ -320,15 +311,11 @@ Partition additions/removals are replicated as well. Previously, partitions had
<listitem>
<!--
Author: Peter Eisentraut <peter@eisentraut.org>
-2020-04-08 [83fd4532a] Allow publishing partition changes via ancestors
+2020-04-06 [f1ac27bfd] Add logical replication support to replicate into partit
-->
<para>
-Allow CREATE PUBLICATION to control whether partitioned tables are published as themselves or their ancestors (Amit Langote)
-</para>
-
-<para>
-The option is publish_via_partition_root.
+Allow non-partitioned tables to be logically replicated to subscribers that receive the rows into partitioned tables (Amit Langote)
</para>
</listitem>
@@ -623,7 +610,7 @@ Author: Noah Misch <noah@leadboat.com>
-->
<para>
-Allow skipping of WAL for new tables and indexes if wal_level is 'minimal' (Noah Misch)
+Allow skipping of WAL for new tables and indexes if wal_level is 'minimal' (Kyotaro Horiguchi)
</para>
<para>
[parent: fb544735f114]