From 7454502f94f6b8addff867f38aa5166eb82c79dc Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Tue, 10 Oct 2023 15:14:19 -0400
Subject: doc: document the need to analyze partitioned tables
Autovacuum does not do it.
Reported-by: Justin Pryzby
Discussion: https://postgr.es/m/20210913035409.GA10647@telsasoft.com
Backpatch-through: 11
---
doc/src/sgml/maintenance.sgml | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 9cf9d030a8a..3018d8f64cf 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -861,10 +861,15 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
- Partitioned tables are not processed by autovacuum. Statistics
- should be collected by running a manual ANALYZE when it is
- first populated, and again whenever the distribution of data in its
- partitions changes significantly.
+ Partitioned tables do not directly store tuples and consequently
+ are not processed by autovacuum. (Autovacuum does process table
+ partitions just like other tables.) Unfortunately, this means that
+ autovacuum does not run ANALYZE on partitioned
+ tables, and this can cause suboptimal plans for queries that reference
+ partitioned table statistics. You can work around this problem by
+ manually running ANALYZE on partitioned tables
+ when they are first populated, and again whenever the distribution
+ of data in their partitions changes significantly.
--
cgit v1.2.3