diff options
Diffstat (limited to 'doc/administration/postgresql/replication_and_failover.md')
| -rw-r--r-- | doc/administration/postgresql/replication_and_failover.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/postgresql/replication_and_failover.md b/doc/administration/postgresql/replication_and_failover.md index 573110d7f57..007762c3c00 100644 --- a/doc/administration/postgresql/replication_and_failover.md +++ b/doc/administration/postgresql/replication_and_failover.md @@ -1242,7 +1242,7 @@ What happens here: - The application still uses the existing leader as its database backend. - The logical replication ensures that the new leader keeps in sync. - When other nodes are added to the new cluster, Patroni handles - the replication to the these nodes. + the replication to the nodes. It is a good idea to wait until the replica nodes of the new cluster are initialized and caught up on the replication lag. |