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 | |
| 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
| -rw-r--r-- | doc/src/sgml/ref/pg_rewind.sgml | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 36e1ee5b191..ee093598ad1 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -221,6 +221,15 @@ PostgreSQL documentation <refsect1> <title>Notes</title> + <para> + When executing <application>pg_rewind</application> using an online + cluster as source which has been recently promoted, it is necessary + to execute a <command>CHECKPOINT</command> after promotion so as its + control file reflects up-to-date timeline information, which is used by + <application>pg_rewind</application> to check if the target cluster + can be rewound using the designated source cluster. + </para> + <refsect2> <title>How it works</title> |