NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit4b482e9

committed

Fix some documentation in pg_rewind

A confusion which comes a lot from users is that it is necessary toissue a checkpoint on a freshly-promoted standby so as its control filehas up-to-date timeline information which is used by pg_rewind tovalidate the operation. Let's document that properly. This isback-patched down to 9.5 where pg_rewind has been introduced.Author: Michael PaquierReviewed-by: Magnus HaganderDiscussion:https://postgr.es/m/CABUevEz5bpvbwVsYCaSMV80CBZ5-82nkMzbb+Bu=h1m=rLdn=g@mail.gmail.comBackpatch-through: 9.5

1 parente9d4cbe commit4b482e9Copy full SHA for 4b482e9

File tree

1 file changed

-0

lines changed

doc/src/sgml/ref
- pg_rewind.sgml

1 file changed

-0

lines changed

`‎doc/src/sgml/ref/pg_rewind.sgml‎`

Lines changed: 9 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -221,6 +221,15 @@ PostgreSQL documentation`
`221`	`221`	`<refsect1>`
`222`	`222`	`<title>Notes</title>`
`223`	`223`
	`224`	`+ <para>`
	`225`	`+ When executing <application>pg_rewind</application> using an online`
	`226`	`+ cluster as source which has been recently promoted, it is necessary`
	`227`	`+ to execute a <command>CHECKPOINT</command> after promotion so as its`
	`228`	`+ control file reflects up-to-date timeline information, which is used by`
	`229`	`+ <application>pg_rewind</application> to check if the target cluster`
	`230`	`+ can be rewound using the designated source cluster.`
	`231`	`+ </para>`
	`232`	`+`
`224`	`233`	`<refsect2>`
`225`	`234`	`<title>How it works</title>`
`226`	`235`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit4b482e9

File tree

1 file changed

1 file changed

`‎doc/src/sgml/ref/pg_rewind.sgml‎`

0 commit comments