On Fri, May 8, 2020 at 12:07:09PM +0900, Amit Langote wrote: > > OK, I used this wording: > > > > Allow logical replication into partitioned tables on subscribers > > (Amit > > Langote) > > > > Previously, subscribers could only receive rows into non-partitioned > > tables. > > This is fine, thanks. > > I have attached a patch with my suggestions above.
OK, I slightly modified the wording of your first change, patch attached. -- Bruce Momjian <br...@momjian.us> https://momjian.us EnterpriseDB https://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
diff --git a/doc/src/sgml/release-13.sgml b/doc/src/sgml/release-13.sgml index 239586c04b..51ebb9b2ba 100644 --- a/doc/src/sgml/release-13.sgml +++ b/doc/src/sgml/release-13.sgml @@ -273,7 +273,7 @@ Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita <para> For example, partitionwise joins can now happen between partitioned -tables where the ancestors do not exactly match. +tables even when their partition bounds do not match exactly. </para> </listitem> @@ -307,7 +307,7 @@ Allow partitioned tables to be logically replicated via publications (Amit Lango <para> 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 their own or their ancestors. +partitioned tables are automatically added/removed from publications. The CREATE PUBLICATION option publish_via_partition_root controls whether changes to partitions are published as their own or their ancestor's. </para> </listitem>
