Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 0a05002

Browse files
committed
pg_rewind: Remove notice in docs about running CHECKPOINT after promote.
Commit 009eeee 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
1 parent b9f0e54 commit 0a05002

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

doc/src/sgml/ref/pg_rewind.sgml

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -335,15 +335,6 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b
335335
</programlisting>
336336
</para>
337337

338-
<para>
339-
When executing <application>pg_rewind</application> using an online
340-
cluster as source which has been recently promoted, it is necessary
341-
to execute a <command>CHECKPOINT</command> after promotion such that its
342-
control file reflects up-to-date timeline information, which is used by
343-
<application>pg_rewind</application> to check if the target cluster
344-
can be rewound using the designated source cluster.
345-
</para>
346-
347338
<refsect2>
348339
<title>How It Works</title>
349340

0 commit comments

Comments
 (0)