From b79e37451947ee985653c6d8a85a3b0adfd04d0c 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 | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index fff53d68286..8ba20ade3ff 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.108 2009/02/07 15:25:51 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.109 2009/02/10 00:55:21 momjian Exp $
PostgreSQL documentation
-->
@@ -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>
--
GitLab