summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-01-07 20:50:49 +0900
committerMichael Paquier <michael@paquier.xyz>2021-01-07 20:50:49 +0900
commit83589107b6cdf34340043239dd93d79b91ac2813 (patch)
tree90c294d6db12bfabbb7cf07712be0938a8a8d254
parent4c20e78f1f154ded6a6a45bf2b6514a1930c17b0 (diff)
doc: Remove reference to recovery params for divergence lookup in pg_rewind
The documentation of pg_rewind mentioned the use of restore_command and primary_conninfo as options available at startup to fetch missing WAL segments that could be used to find the point of divergence for the rewind. This is confusing because when finding the point of divergence the target cluster is offline, so this option is not available. Issue introduced by 878bd9a, so backpatch down to 9.6. The documentation of 13 and HEAD was already right as this sentence has been changed by a7e8ece when introducing -c/--restore-target-wal. Reported-by: Amine Tengilimoglu Discussion: https://postgr.es/m/CADTdw-w_0MP=iQrfizeU4QU5fcZb+w8P_oPeLL+WznWf0kbn3w@mail.gmail.com Backpatch-through: 9.6
-rw-r--r--doc/src/sgml/ref/pg_rewind.sgml9
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 94517d607d8..e6a5279215e 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_wal</> 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_wal</> 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>