diff options
| -rw-r--r-- | doc/src/sgml/ref/pg_rewind.sgml | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index f231646ee9b..096ae655564 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -68,11 +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_xlog</> directory, or - fetched on startup by configuring <filename>recovery.conf</>. The use of - <application>pg_rewind</> 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_xlog</> directory. + The use of <application>pg_rewind</> 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> |