Commitc552e17

committed

docs: clarify new aggressive vacuum mode for multi-xacts

1 parent50371df commitc552e17Copy full SHA for c552e17

File tree

-8

lines changed

-8

lines changed

Lines changed: 8 additions & 8 deletions

Original file line number	Diff line number	Diff line change
`@@ -697,14 +697,14 @@ HINT: Stop the postmaster and vacuum that database in single-user mode.`
`697`	`697`	`</para>`
`698`	`698`
`699`	`699`	`<para>`
`700`		`- As a safety device, an aggressive vacuum scan will occur for any table`
`701`		`- whose multixact-ageis greater than`
`702`		`-<xreflinkend="guc-autovacuum-multixact-freeze-max-age"/>. Aggressive`
`703`		`-vacuum scans will also occur progressively for all tables, starting with`
`704`		`-those that have the oldest multixact-age, if the amount of used member`
`705`		`-storage space exceeds the amount 50% of the addressable storage space.`
`706`		`- Both of these kinds of aggressive scans will occur even if autovacuum is`
`707`		`- nominally disabled.`
	`700`	`+ As a safety device, an aggressive vacuum scan will`
	`701`	`+occur for any tablewhose multixact-age(see <xref`
	`702`	`+ linkend="vacuum-for-multixact-wraparound"/>) is greater than <xref`
	`703`	`+linkend="guc-autovacuum-multixact-freeze-max-age"/>. Also, if the`
	`704`	`+storage occupied by multixacts members exceeds 2GB, aggressive vacuum`
	`705`	`+scans will occur more often for all tables, starting with those that`
	`706`	`+have the oldest multixact-age.Both of these kinds of aggressive`
	`707`	`+scans will occur even if autovacuum isnominally disabled.`
`708`	`708`	`</para>`
`709`	`709`	`</sect3>`
`710`	`710`	`</sect2>`

Comments

(0)