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

Commit b79e374

Browse files
committed
Update wording of how to prevent pg_dump from affecting statistics
collection.
1 parent 8205258 commit b79e374

File tree

1 file changed

+5
-6
lines changed

1 file changed

+5
-6
lines changed

doc/src/sgml/ref/pg_dump.sgml

+5-6
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.108 2009/02/07 15:25:51 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.109 2009/02/10 00:55:21 momjian Exp $
33
PostgreSQL documentation
44
-->
55

@@ -759,16 +759,15 @@ PostgreSQL documentation
759759
variables used by the <application>libpq</application> front-end
760760
library will apply.
761761
</para>
762+
762763
<para>
763764
The database activity of <application>pg_dump</application> is
764765
normally collected by the statistics collector. If this is
765-
undesirable, you can set parameters <literal>stats_block_level</literal>
766-
and <literal>stats_row_level</literal> to false via the
767-
<application>libpq</> <envar>PGOPTIONS</envar> environment variable,
768-
or via <literal>ALTER USER</literal>.
766+
undesirable, you can set parameter <literal>track_counts</literal>
767+
to false via <envar>PGOPTIONS</envar> or the <literal>ALTER
768+
USER</literal> command.
769769
</para>
770770

771-
772771
</refsect1>
773772

774773

0 commit comments

Comments
 (0)