Commit4d966cc

committed

doc: document the need to analyze partitioned tables

Autovacuum does not do it.Reported-by: Justin PryzbyDiscussion:https://postgr.es/m/20210913035409.GA10647@telsasoft.comBackpatch-through: 11

1 parent6615bb9 commit4d966ccCopy full SHA for 4d966cc

File tree

-4

lines changed

-4

lines changed

Lines changed: 9 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -841,10 +841,15 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu`
`841`	`841`	`</para>`
`842`	`842`
`843`	`843`	`<para>`
`844`		`- Partitioned tables are not processed by autovacuum. Statistics`
`845`		`- should be collected by running a manual <command>ANALYZE</command> when it is`
`846`		`- first populated, and again whenever the distribution of data in its`
`847`		`- partitions changes significantly.`
	`844`	`+ Partitioned tables do not directly store tuples and consequently`
	`845`	`+ are not processed by autovacuum. (Autovacuum does process table`
	`846`	`+ partitions just like other tables.) Unfortunately, this means that`
	`847`	`+ autovacuum does not run <command>ANALYZE</command> on partitioned`
	`848`	`+ tables, and this can cause suboptimal plans for queries that reference`
	`849`	`+ partitioned table statistics. You can work around this problem by`
	`850`	`+ manually running <command>ANALYZE</command> on partitioned tables`
	`851`	`+ when they are first populated, and again whenever the distribution`
	`852`	`+ of data in their partitions changes significantly.`
`848`	`853`	`</para>`
`849`	`854`
`850`	`855`	`<para>`

Comments

(0)