aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2024-08-19 18:27:21 -0400
committerBruce Momjian <bruce@momjian.us>2024-08-19 18:27:21 -0400
commitef3aa800e884ba30f21ed1f36bdc587e67df39e5 (patch)
treee66f3cb8cc1fc02b1cb3953dc8f2d60e84e62ef0
parent11f1218ce81ef3ce98389754456ca9365fa10dbe (diff)
downloadpostgresql-ef3aa800e884ba30f21ed1f36bdc587e67df39e5.tar.gz
postgresql-ef3aa800e884ba30f21ed1f36bdc587e67df39e5.zip
doc: Improve vague pg_createsubscriber description
Discussion: https://postgr.es/m/ZqX_4J-nFTQtmj6K@momjian.us Author: Euler Taveira Backpatch-through: 17
-rw-r--r--doc/src/sgml/ref/pg_createsubscriber.sgml7
1 files 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>