<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.106 2009/01/05 16:54:36 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.107 2009/02/07 14:31:30 momjian Exp $
PostgreSQL documentation
-->
<varlistentry>
<term><envar>PGDATABASE</envar></term>
<term><envar>PGHOST</envar></term>
+ <term><envar>PGOPTIONS</envar></term>
<term><envar>PGPORT</envar></term>
- <term><envar>PGUSER</envar></term>
+ <term><envar>PGUSER</envar></term>
<listitem>
<para>
Default connection parameters.
</para>
</listitem>
+
</varlistentry>
</variablelist>
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>.
+ </para>
+
+
</refsect1>
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.74 2009/01/05 16:54:36 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.75 2009/02/07 14:31:30 momjian Exp $
PostgreSQL documentation
-->
<variablelist>
<varlistentry>
<term><envar>PGHOST</envar></term>
+ <term><envar>PGOPTIONS</envar></term>
<term><envar>PGPORT</envar></term>
<term><envar>PGUSER</envar></term>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.78 2009/02/02 20:07:36 adunstan Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.79 2009/02/07 14:31:30 momjian Exp $ -->
<refentry id="APP-PGRESTORE">
<refmeta>
<variablelist>
<varlistentry>
<term><envar>PGHOST</envar></term>
+ <term><envar>PGOPTIONS</envar></term>
<term><envar>PGPORT</envar></term>
<term><envar>PGUSER</envar></term>