Commit0a05002

committed

pg_rewind: Remove notice in docs about running CHECKPOINT after promote.

Commit009eeee made it unnecessary. pg_rewind now works on arecently promoted standby.Author: Kyotaro Horiguchi, Keisuke KurodaDiscussion:https://www.postgresql.org/message-id/aeb5f31a-8de2-40a8-64af-ab659a309d6b%40iki.fi

1 parentb9f0e54 commit0a05002Copy full SHA for 0a05002

File tree

-9

lines changed

-9

lines changed

Lines changed: 0 additions & 9 deletions

Original file line number	Diff line number	Diff line change
`@@ -335,15 +335,6 @@ GRANT EXECUTE ON function pg_catalog.pg_read_binary_file(text, bigint, bigint, b`
`335`	`335`	`</programlisting>`
`336`	`336`	`</para>`
`337`	`337`
`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`		`-`
`347`	`338`	`<refsect2>`
`348`	`339`	`<title>How It Works</title>`
`349`	`340`

Comments

(0)