Bruce Momjian wrote:
Apologies. Turns out the name of the relevant setting was changed
for 8.3! So a revised patch is attached.
For backing, see:
http://www.postgresql.org/docs/8.3/static/release-8-3.html
" Numerous changes in administrative server parameters...
stats_block_level and stats_row_level are merged into track_counts."
Bryce Nesbitt wrote:
We don't want a pg_dump flag; the doc mention is good enough.
Doh! Try this one instead. Postgres 8.3 changed the name of the flag
mentioned in the doc.
|
Index: ref/pg_dump.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v
retrieving revision 1.108
diff -c -2 -r1.108 pg_dump.sgml
*** ref/pg_dump.sgml 7 Feb 2009 15:25:51 -0000 1.108
--- ref/pg_dump.sgml 9 Feb 2009 20:19:48 -0000
***************
*** 760,773 ****
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>
--- 760,772 ----
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 parameter
! <literal>track_counts</literal> to false via <envar>PGOPTIONS</envar>
! or the <literal>ALTER USER</literal> command. For versions prior to 8.3, set
! <literal>stats_block_level</literal> and <literal>stats_row_level</literal> instead.
</para>
</refsect1>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
