diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:38:26 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:38:26 +0900 |
| commit | 4b482e94a006ee3ed6df09aba8c526cdcee84496 (patch) | |
| tree | cad536d947220c29f6cdcf1c90bde38fec573276 /src/backend/executor/nodeModifyTable.c | |
| parent | e9d4cbeacb553fc5f4c185ec1156018ea4114fdd (diff) | |
| download | postgresql-4b482e94a006ee3ed6df09aba8c526cdcee84496.tar.gz postgresql-4b482e94a006ee3ed6df09aba8c526cdcee84496.zip | |
Fix some documentation in pg_rewind
A confusion which comes a lot from users is that it is necessary to
issue a checkpoint on a freshly-promoted standby so as its control file
has up-to-date timeline information which is used by pg_rewind to
validate the operation. Let's document that properly. This is
back-patched down to 9.5 where pg_rewind has been introduced.
Author: Michael Paquier
Reviewed-by: Magnus Hagander
Discussion: https://postgr.es/m/CABUevEz5bpvbwVsYCaSMV80CBZ5-82nkMzbb+Bu=h1m=rLdn=g@mail.gmail.com
Backpatch-through: 9.5
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions