From 3db034600b5ec5e99b7c8f1d3925f37aa4a97f46 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 10 Feb 2009 00:55:21 +0000
Subject: [PATCH] Update wording of how to prevent pg_dump from affecting
 statistics collection.

---
 doc/src/sgml/ref/pg_dump.sgml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 5ed6d085ac..9cbff3c710 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -759,16 +759,15 @@ PostgreSQL documentation
    variables used by the <application>libpq</application> front-end
    library will apply.
   </para>
+
   <para>
    The database activity of <application>pg_dump</application> is
    normally collected by the statistics collector.  If this is
-   undesirable, you can set parameters <literal>stats_block_level</literal>
-   and <literal>stats_row_level</literal> to false via the
-   <application>libpq</> <envar>PGOPTIONS</envar> environment variable,
-   or via <literal>ALTER USER</literal>.
+   undesirable, you can set parameter <literal>track_counts</literal>
+   to false via <envar>PGOPTIONS</envar> or the <literal>ALTER
+   USER</literal> command.
   </para>
 
-
  </refsect1>
 
 
-- 
2.39.5