postgres.git / summary / log / commit / refs

commit    ef3aa800e884ba30f21ed1f36bdc587e67df39e5
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Mon Aug 19 22:27:21 2024 +0000
First released in: 18.0, 17.0

    doc:  Improve vague pg_createsubscriber description
    
    Discussion: https://postgr.es/m/ZqX_4J-nFTQtmj6K@momjian.us
    
    Author: Euler Taveira
    
    Backpatch-through: 17


 doc/src/sgml/ref/pg_createsubscriber.sgml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/ref/pg_createsubscriber.sgml b/doc/src/sgml/ref/pg_createsubscriber.sgml
index 026290e0114..35b2fa9b9be 100644
--- a/doc/src/sgml/ref/pg_createsubscriber.sgml
+++ b/doc/src/sgml/ref/pg_createsubscriber.sgml
@@ -57,9 +57,10 @@ PostgreSQL documentation
   <para>
    After a successful run, the state of the target server is analogous to a
    fresh logical replication setup.  The main difference between the logical
-   replication setup and <application>pg_createsubscriber</application> is the
-   initial data copy.  It does only the synchronization phase, which ensures
-   each table is brought up to a synchronized state.
+   replication setup and <application>pg_createsubscriber</application> is how
+   the data synchronization is done. <application>pg_createsubscriber</application>
+   does not copy the initial table data. It does only the synchronization phase,
+   which ensures each table is brought up to a synchronized state.
   </para>
 
   <para>


[parent: 11f1218ce81e]