Doc: fix column list vs. replica identity rules.

It was not strictly correct to say that a column list must always include
replica identity columns because that is true for only updates and
deletes.

Author: Peter Smith
Reviwed-by: Vignesh C, Amit Kapila
Backpatch-through: 15, where it was introduced
Discussion: https://postgr.es/m/CAHut+PvOuc9=_4TbASc5=VUqh16UWtFO3GzcKQK_5m1hrW3vqg@mail.gmail.com

diff --git a/doc/src/sgml/ref/create_publication.sgml b/doc/src/sgml/ref/create_publication.sgml
index 5790d762705232830e36943c55de4a127e610acc..b0d59ef47d2b51d4d68184f9351cc215d9c5cc87 100644 (file)
--- a/doc/src/sgml/ref/create_publication.sgml
+++ b/doc/src/sgml/ref/create_publication.sgml
@@ -90,8 +90,8 @@ CREATE PUBLICATION name
      
       When a column list is specified, only the named columns are replicated.
       If no column list is specified, all columns of the table are replicated
-      through this publication, including any columns added later.  If a column
-      list is specified, it must include the replica identity columns.
+      through this publication, including any columns added later. It has no
+      effect on TRUNCATE commands.
      
 
      
@@ -252,6 +252,13 @@ CREATE PUBLICATION name
    disallowed on those tables.
   
 
+  
+   Any column list must include the REPLICA IDENTITY columns
+   in order for UPDATE or DELETE
+   operations to be published. There are no column list restrictions if the
+   publication publishes only INSERT operations.
+  
+
   
    A row filter expression (i.e., the WHERE clause) must contain only
    columns that are covered by the REPLICA IDENTITY, in