From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 19 Aug 2024 22:27:22 +0000 (-0400)
Subject: doc:  Improve vague pg_createsubscriber description
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=6467993fb552bda7fc1f615d90a66a16583e9998;p=postgresql.git

doc:  Improve vague pg_createsubscriber description

Discussion: https://postgr.es/m/ZqX_4J-nFTQtmj6K@momjian.us

Author: Euler Taveira

Backpatch-through: 17
---

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>