Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 4a96908

Browse files
committed
Document new 9.0 behavior of ANALYZE on inheritance hierarchies.
In particular, note that autovacuum does not yet understand that it might need to vacuum inheritance parents as a result of changes to the child tables.
1 parent 48a7245 commit 4a96908

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

doc/src/sgml/ref/analyze.sgml

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/analyze.sgml,v 1.29 2010/04/03 07:22:57 petere Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/analyze.sgml,v 1.30 2010/06/15 18:43:35 rhaas Exp $
33
PostgreSQL documentation
44
-->
55

@@ -176,6 +176,17 @@ ANALYZE [ VERBOSE ] [ <replaceable class="PARAMETER">table</replaceable> [ ( <re
176176
<command>ALTER TABLE ... ALTER COLUMN ... SET (n_distinct = ...)</>
177177
(see <xref linkend="sql-altertable">).
178178
</para>
179+
180+
<para>
181+
If the table being analyzed has one or more children,
182+
<command>ANALYZE</command> will gather statistics twice: once on the
183+
rows of the parent table only, and a second time on the rows of the
184+
parent table with all of its children. The autovacuum daemon, however,
185+
will only consider inserts or updates on the parent table when deciding
186+
whether to trigger an automatic analyze. If that table is rarely
187+
inserted into or updated, the inheritance statistics will not be up to date
188+
unless you run <command>ANALYZE</command> manually.
189+
</para>
179190
</refsect1>
180191

181192
<refsect1>

0 commit comments

Comments
 (0)