From: Michael Paquier Date: Mon, 27 Apr 2026 07:17:04 +0000 (+0900) Subject: doc: Fix grammar in some logical replication pages X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=31b9d90f15a57bca72128d512ae7ae624e6b1c93;p=thirdparty%2Fpostgresql.git doc: Fix grammar in some logical replication pages Author: Peter Smith Discussion: https://postgr.es/m/CAHut+PuvY_wYLPJ4DTs7NE9Lu2ty4d-OgZAOJC-NvCM=2wwcQQ@mail.gmail.com Backpatch-through: 14 --- diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index c06d255d2ed..9e7868487de 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -41,14 +41,14 @@ Sending incremental changes in a single database or a subset of a - database to subscribers as they occur + database to subscribers as they occur. Sending a subset of the database to multiple databases (i.e., - broadcast) + broadcast). @@ -61,14 +61,14 @@ - Replicating between different major versions of PostgreSQL + Replicating between different major versions of PostgreSQL. Replicating between PostgreSQL instances on different platforms (for - example Linux to Windows) + example Linux to Windows). @@ -90,7 +90,7 @@ The subscriber database behaves in the same way as any other PostgreSQL instance and can be used as a publisher for other databases by defining its - own publications. When the subscriber is treated as read-only by + own publications. When the subscriber is treated as read-only by an application, there will be no conflicts from a single subscription. On the other hand, if there are other writes done either by an application or by other subscribers to the same set of tables, conflicts can arise. @@ -211,8 +211,8 @@ A subscription is the downstream side of logical replication. The node where a subscription is defined is referred to as the subscriber. A subscription defines the connection - to another database and set of publications (one or more) to which it wants - to subscribe. + to another database and the set of publications (one or more) to which it + wants to subscribe. @@ -988,7 +988,7 @@ HINT: To initiate replication, you must manually create the replication slot, e - If the subscriber is in a release prior to 15, copy pre-existing data + If the subscriber is in a release prior to 15, copying pre-existing data doesn't use row filters even if they are defined in the publication. This is because old releases can only copy the entire table data. @@ -2458,7 +2458,7 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER Initial Snapshot - The initial data in existing subscribed tables are snapshotted and + The initial data in existing subscribed tables is snapshotted and copied in parallel instances of a special kind of apply process. These special apply processes are dedicated table synchronization workers, spawned for each table to be synchronized. Each table diff --git a/doc/src/sgml/ref/alter_subscription.sgml b/doc/src/sgml/ref/alter_subscription.sgml index f215fb0e5a2..e4f0b6b16c7 100644 --- a/doc/src/sgml/ref/alter_subscription.sgml +++ b/doc/src/sgml/ref/alter_subscription.sgml @@ -331,7 +331,7 @@ ALTER SUBSCRIPTION name RENAME TO < process reports an error if any prepared transactions done by the logical replication worker (from when two_phase parameter was still true) are found. You can resolve - prepared transactions on the publisher node, or manually roll back them + prepared transactions on the publisher node, or manually roll them back on the subscriber, and then try again. The transactions prepared by logical replication worker corresponding to a particular subscription have the following pattern: pg_gid_%u_%u diff --git a/doc/src/sgml/ref/create_publication.sgml b/doc/src/sgml/ref/create_publication.sgml index 0ac576d3f10..f82d640e6ca 100644 --- a/doc/src/sgml/ref/create_publication.sgml +++ b/doc/src/sgml/ref/create_publication.sgml @@ -157,7 +157,7 @@ CREATE PUBLICATION name - When a partitioned table is published via schema level publication, all + When a partitioned table is published via a schema-level publication, all of its existing and future partitions are implicitly considered to be part of the publication, regardless of whether they are from the publication schema or not. So, even operations that are performed directly on a @@ -238,7 +238,7 @@ CREATE PUBLICATION name This parameter determines which DML operations will be published by - the new publication to the subscribers. The value is + the new publication to the subscribers. The value is a comma-separated list of operations. The allowed operations are insert, update, delete, and truncate. @@ -278,7 +278,7 @@ CREATE PUBLICATION name If the subscriber is from a release prior to 18, then initial table - synchronization won't copy generated columns even if parameter + synchronization won't copy generated columns even if the parameter publish_generated_columns is stored in the publisher.