Dept of second thoughts: recursive case in ANALYZE shouldn't emit a

pgstats message.  This might need to be done differently later, but
with the current logic that's what should happen.

diff --git a/src/backend/commands/analyze.c b/src/backend/commands/analyze.c
index aa41cd3d4c474dcb36de9c4db1a7c6a6929ee5f3..5946c4a8307f373b2d16a5f895d66a284f0445fa 100644 (file)
--- a/src/backend/commands/analyze.c
+++ b/src/backend/commands/analyze.c
@@ -8,7 +8,7 @@
  *
  *
  * IDENTIFICATION
- *   $PostgreSQL: pgsql/src/backend/commands/analyze.c,v 1.145 2009/12/30 20:32:14 tgl Exp $
+ *   $PostgreSQL: pgsql/src/backend/commands/analyze.c,v 1.146 2009/12/30 21:21:33 tgl Exp $
  *
  *-------------------------------------------------------------------------
  */
@@ -565,9 +565,12 @@ do_analyze_rel(Relation onerel, VacuumStmt *vacstmt,
    /*
     * Report ANALYZE to the stats collector, too; likewise, tell it to
     * adopt these numbers only if we're not inside a VACUUM that got a
-    * better number.
+    * better number.  However, a call with inh = true shouldn't reset
+    * the stats.
     */
-   pgstat_report_analyze(onerel, update_reltuples, totalrows, totaldeadrows);
+   if (!inh)
+       pgstat_report_analyze(onerel, update_reltuples,
+                             totalrows, totaldeadrows);
 
    /* We skip to here if there were no analyzable columns */
 cleanup: