diff options
author | Heikki Linnakangas | 2023-02-27 07:34:43 +0000 |
---|---|---|
committer | Heikki Linnakangas | 2023-02-27 07:34:43 +0000 |
commit | 0a0500207a94185e73373d7056a22e41de8f9d64 (patch) | |
tree | 3edc026c1478b9c5ba75fcd1efb7f44a0bef31b9 | |
parent | b9f0e54bc955ba3f6187d238b03c9c99c576a6af (diff) |
pg_rewind: Remove notice in docs about running CHECKPOINT after promote.
Commit 009eeee746 made it unnecessary. pg_rewind now works on a
recently promoted standby.
Author: Kyotaro Horiguchi, Keisuke Kuroda
Discussion: https://www.postgresql.org/message-id/aeb5f31a-8de2-40a8-64af-ab659a309d6b%40iki.fi
-rw-r--r-- | doc/src/sgml/ref/pg_rewind.sgml | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/doc/src/sgml/ref/pg_rewind.sgml b/doc/src/sgml/ref/pg_rewind.sgml index 768024c491..9118f05bf2 100644 --- a/doc/src/sgml/ref/pg_rewind.sgml +++ b/doc/src/sgml/ref/pg_rewind.sgml @@ -335,15 +335,6 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b </programlisting> </para> - <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 such that 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> |