postgres.git / summary / log / commit / refs

commit    a8d747771fe59cd3cf7bc16029a3e4d01407a864
Author:   Amit Kapila <akapila@postgresql.org>
Date:     Tue Jun 11 03:45:14 2024 +0000
First released in: 17.0, 15.8, 16.4

    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


 doc/src/sgml/logical-replication.sgml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml
index 4abfb32f77b..e6096c67e06 100644
--- a/doc/src/sgml/logical-replication.sgml
+++ b/doc/src/sgml/logical-replication.sgml
@@ -1109,9 +1109,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>


[parent: 2eba27571edc]