aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-01-07 20:50:35 +0900
committerMichael Paquier <michael@paquier.xyz>2021-01-07 20:50:35 +0900
commit820f882b3b4aa3c5f521cc1c83737a4958eb3e3f (patch)
tree0c0242ef08a751514964f5ab55ecc6165b805262 /src/backend/tcop/postgres.c
parent9f540f840665936132dd30bd8e58e9a67e648f22 (diff)
downloadpostgresql-820f882b3b4aa3c5f521cc1c83737a4958eb3e3f.tar.gz
postgresql-820f882b3b4aa3c5f521cc1c83737a4958eb3e3f.zip
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
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions