Doc: Fix ambuiguity in column lists.

The behavior for columns added later to the table for publications with no
specified column lists was not clear.

Reported-by: Koen De Groote
Author: Peter Smith
Reviewed-by: Vignesh C, Laurenz Albe
Backpatch-through: 15
Discussion: https://postgr.es/m/171621878740.686.11325940592820985181@wrigleys.postgresql.org

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index befc9e2708e2fbd8b13bc318c18f794509181fa0..746d5bd330ca370ed2a1c30278c2afe4730dda73 100644 (file)
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -1382,9 +1382,9 @@ test_sub=# SELECT * FROM child ORDER BY a;
   </para>
 
   <para>
-   If no column list is specified, any columns added later are automatically
-   replicated. This means that having a column list which names all columns
-   is not the same as having no column list at all.
+   If no column list is specified, any columns added to the table later are
+   automatically replicated. This means that having a column list which names
+   all columns is not the same as having no column list at all.
   </para>
 
   <para>