diff options
| -rw-r--r-- | doc/src/sgml/ref/pg_rewind.sgml | 10 |
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 3ccb9554877..58addfcb96d 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -68,12 +68,10 @@ PostgreSQL documentation shut down soon after the divergence, this is not a problem, but if the target cluster ran for a long time after the divergence, the old WAL files might no longer be present. In that case, they can be manually - copied from the WAL archive to the <filename>pg_wal</filename> directory, or - fetched on startup by configuring <xref linkend="guc-primary-conninfo"/> or - <xref linkend="guc-restore-command"/>. The use of - <application>pg_rewind</application> is not limited to failover, e.g., a standby - server can be promoted, run some write transactions, and then rewound - to become a standby again. + copied from the WAL archive to the <filename>pg_wal</filename> directory. + The use of <application>pg_rewind</application> is not limited to + failover, e.g., a standby server can be promoted, run some write + transactions, and then rewound to become a standby again. </para> <para> |