Commitad385a4

committed

docs: Note the recovery_min_apply_delay bloats pg_wal.

Those WAL files that we're waiting to apply have to be storedsomewhere.Thom BrownDiscussion:http://postgr.es/m/CAA-aLv4SkJRK6GGcd0Axt8kt6_eWMEbtG7f8NJpFh+rNshtdNA@mail.gmail.com

1 parente0064f0 commitad385a4Copy full SHA for ad385a4

File tree

-0

lines changed

-0

lines changed

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -4872,6 +4872,12 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="`
`4872`	`4872`	`state, until the standby is promoted or triggered. After that the standby`
`4873`	`4873`	`will end recovery without further waiting.`
`4874`	`4874`	`</para>`
	`4875`	`+ <para>`
	`4876`	`+ WAL records must be kept on the standby until they are ready to be`
	`4877`	`+ applied. Therefore, longer delays will result in a greater accumulation`
	`4878`	`+ of WAL files, increasing disk space requirements for the standby's`
	`4879`	`+ <filename>pg_wal</filename> directory.`
	`4880`	`+ </para>`
`4875`	`4881`	`<para>`
`4876`	`4882`	`This parameter is intended for use with streaming replication deployments;`
`4877`	`4883`	`however, if the parameter is specified it will be honored in all cases`

Comments

(0)