diff options
| author | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:38:47 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2019-04-05 10:38:47 +0900 |
| commit | 1f63f69c43b5709cf6d8fe60be5e4f137c157316 (patch) | |
| tree | 922635526fe026859a9968b88c9087145ddf907e | |
| parent | e9559e7add5f91befb64f8a9e8c9e4a7d2074828 (diff) | |
| download | postgresql-1f63f69c43b5709cf6d8fe60be5e4f137c157316.tar.gz postgresql-1f63f69c43b5709cf6d8fe60be5e4f137c157316.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 ed1625b5237..d303bfd7623 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -217,6 +217,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> |