postgres.git / summary / log / commit / refs

commit    eb7828f54a44843a64a23d0891d7eb6018c0749e
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Wed Dec 01 04:37:45 2021 +0000
First released in: 15.0, 13.6, 14.2

    Doc: Add "Attach Partition" limitation during logical replication.
    
    ATTACHing a table into a partition tree whose root is published using a
    publication with publish_via_partition_root set to true does not result in
    the table's existing contents being replicated. This happens because
    subscriber doesn't consider replicating the newly attached partition as
    the root table is already in a 'ready' state.
    
    This behavior was introduced in PG13 (83fd4532a7) where we allowed to
    publish partition changes via ancestors.
    
    We can consider fixing this limitation in the future.
    
    Author: Amit Langote
    Reviewed-by: Hou Zhijie, Amit Kapila
    Backpatch-through: 13
    Discussion: https://postgr.es/m/OS0PR01MB5716E97F00732B52DC2BBC2594989@OS0PR01MB5716.jpnprd01.prod.outlook.com


 doc/src/sgml/ref/create_publication.sgml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/src/sgml/ref/create_publication.sgml b/doc/src/sgml/ref/create_publication.sgml
index 4aeb0c88313..d805e8e77a7 100644
--- a/doc/src/sgml/ref/create_publication.sgml
+++ b/doc/src/sgml/ref/create_publication.sgml
@@ -232,6 +232,13 @@ CREATE PUBLICATION <replaceable class="parameter">name</replaceable>
    <command>UPDATE</command>, or it may not be published at all.
   </para>
 
+  <para>
+   <command>ATTACH</command>ing a table into a partition tree whose root is
+   published using a publication with <literal>publish_via_partition_root</literal>
+   set to <literal>true</literal> does not result in the table's existing contents
+   being replicated.
+  </para>
+
   <para>
    <command>COPY ... FROM</command> commands are published
    as <command>INSERT</command> operations.


[parent: 9270778f467d]