Tom,
> It's gone. You might want to crosscheck the docs against the CVS-tip
> version of guc.c ...
Well, I did 2 weeks ago when I started this process. I'll do it again before
beta.
In the meantime, here's a new patch for runtime.sgml, based on today's CVS:
1) drops SHOW_BTREE
2) drops HAS_RENDEZVOUS
3) Folds the redundant "Statistics" section into Logging and Query Tuning,
depending on the option.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
? runtime-sgml.patch
Index: runtime.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v
retrieving revision 1.187
diff -r1.187 runtime.sgml
1396a1397,1459
> <sect3 id="runtime-config-query-statistics">
> <title>Query and Index Statistics Collector</title>
> <variablelist>
>
> <varlistentry>
> <term><varname>STATS_START_COLLECTOR</varname> (<type>boolean</type>)</term>
> <listitem>
> <para>
> Controls whether the server should start the
> statistics-collection subprocess. This is on by default, but
> may be turned off if you know you have no interest in
> collecting statistics. This option can only be set at server
> start.
> </para>
> </listitem>
> </varlistentry>
>
> <varlistentry>
> <term><varname>STATS_COMMAND_STRING</varname> (<type>boolean</type>)</term>
> <listitem>
> <para>
> Enables the collection of statistics on the currently
> executing command of each session, along with the time at
> which that command began execution. This option is off by
> default. Note that even when enabled, this information is not
> visible to all users, only to superusers and the user owning
> the session being reported on; so it should not represent a
> security risk. This data can be accessed via the
> <structname>pg_stat_activity</structname> system view; refer
> to <xref linkend="monitoring"> for more information.
> </para>
> </listitem>
> </varlistentry>
>
> <varlistentry>
> <term><varname>STATS_BLOCK_LEVEL</varname> (<type>boolean</type>)</term>
> <term><varname>STATS_ROW_LEVEL</varname> (<type>boolean</type>)</term>
> <listitem>
> <para>
> These enable the collection of block-level and row-level statistics
> on database activity, respectively. These options are off by
> default. This data can be accessed via the
> <structname>pg_stat</structname> and
> <structname>pg_statio</structname> family of system views;
> refer to <xref linkend="monitoring"> for more information.
> </para>
> </listitem>
> </varlistentry>
>
> <varlistentry>
> <term><varname>STATS_RESET_ON_SERVER_START</varname> (<type>boolean</type>)</term>
> <listitem>
> <para>
> If on, collected statistics are zeroed out whenever the server
> is restarted. If off, statistics are accumulated across server
> restarts. The default is on. This option can only be set at
> server start.
> </para>
> </listitem>
> </varlistentry>
>
> </variablelist>
> </sect3>
1808a1872,1905
>
> <sect3 id="runtime-config-logging-statistics">
> <title>Statistics Logging</title>
> <variablelist>
>
> <varlistentry>
> <term><varname>LOG_STATEMENT_STATS</varname> (<type>boolean</type>)</term>
> <term><varname>LOG_PARSER_STATS</varname> (<type>boolean</type>)</term>
> <term><varname>LOG_PLANNER_STATS</varname> (<type>boolean</type>)</term>
> <term><varname>LOG_EXECUTOR_STATS</varname> (<type>boolean</type>)</term>
> <listitem>
> <para>
> For each query, write performance statistics of the respective
> module to the server log. This is a crude profiling
> instrument.
> </para>
> </listitem>
> </varlistentry>
>
> <varlistentry>
> <term><varname>DEFAULT_STATISTICS_TARGET</varname> (<type>integer</type>)</term>
> <listitem>
> <para>
> Sets the default statistics target for table columns that have not
> had a column-specific target set via <command>ALTER TABLE SET
> STATISTICS</>. Larger values increase the time needed to do
> <command>ANALYZE</>, but may improve the quality of the planner's
> estimates. The default value is 10.
> </para>
> </listitem>
> </varlistentry>
>
> </variablelist>
> </sect3>
2156,2189d2252
< <sect2 id="runtime-config-statistics">
< <title>Statistics</title>
<
< <sect3 id="runtime-config-statistics-monitor">
< <title>Statistics Monitoring</title>
< <variablelist>
<
< <varlistentry>
< <term><varname>LOG_STATEMENT_STATS</varname> (<type>boolean</type>)</term>
< <term><varname>LOG_PARSER_STATS</varname> (<type>boolean</type>)</term>
< <term><varname>LOG_PLANNER_STATS</varname> (<type>boolean</type>)</term>
< <term><varname>LOG_EXECUTOR_STATS</varname> (<type>boolean</type>)</term>
< <listitem>
< <para>
< For each query, write performance statistics of the respective
< module to the server log. This is a crude profiling
< instrument.
< </para>
< </listitem>
< </varlistentry>
<
< <varlistentry>
< <term><varname>DEFAULT_STATISTICS_TARGET</varname> (<type>integer</type>)</term>
< <listitem>
< <para>
< Sets the default statistics target for table columns that have not
< had a column-specific target set via <command>ALTER TABLE SET
< STATISTICS</>. Larger values increase the time needed to do
< <command>ANALYZE</>, but may improve the quality of the planner's
< estimates. The default value is 10.
< </para>
< </listitem>
< </varlistentry>
<
2191,2256d2253
< </variablelist>
< </sect3>
< <sect3 id="runtime-config-statistics-collector">
< <title>Query and Index Statistics Collector</title>
< <variablelist>
<
< <varlistentry>
< <term><varname>STATS_START_COLLECTOR</varname> (<type>boolean</type>)</term>
< <listitem>
< <para>
< Controls whether the server should start the
< statistics-collection subprocess. This is on by default, but
< may be turned off if you know you have no interest in
< collecting statistics. This option can only be set at server
< start.
< </para>
< </listitem>
< </varlistentry>
<
< <varlistentry>
< <term><varname>STATS_COMMAND_STRING</varname> (<type>boolean</type>)</term>
< <listitem>
< <para>
< Enables the collection of statistics on the currently
< executing command of each session, along with the time at
< which that command began execution. This option is off by
< default. Note that even when enabled, this information is not
< visible to all users, only to superusers and the user owning
< the session being reported on; so it should not represent a
< security risk. This data can be accessed via the
< <structname>pg_stat_activity</structname> system view; refer
< to <xref linkend="monitoring"> for more information.
< </para>
< </listitem>
< </varlistentry>
<
< <varlistentry>
< <term><varname>STATS_BLOCK_LEVEL</varname> (<type>boolean</type>)</term>
< <term><varname>STATS_ROW_LEVEL</varname> (<type>boolean</type>)</term>
< <listitem>
< <para>
< These enable the collection of block-level and row-level statistics
< on database activity, respectively. These options are off by
< default. This data can be accessed via the
< <structname>pg_stat</structname> and
< <structname>pg_statio</structname> family of system views;
< refer to <xref linkend="monitoring"> for more information.
< </para>
< </listitem>
< </varlistentry>
<
< <varlistentry>
< <term><varname>STATS_RESET_ON_SERVER_START</varname> (<type>boolean</type>)</term>
< <listitem>
< <para>
< If on, collected statistics are zeroed out whenever the server
< is restarted. If off, statistics are accumulated across server
< restarts. The default is on. This option can only be set at
< server start.
< </para>
< </listitem>
< </varlistentry>
<
< </variablelist>
< </sect3>
< </sect2>
2365,2373d2361
< <term><varname>HAS_RENDEZVOUS</varname> (<type>boolean</type>)</term>
< <indexterm><primary>rendezvous</></>
< <listitem>
< <para>
< </para>
< </listitem>
< </varlistentry>
<
< <varlistentry>
2470d2457
< <term><varname>SHOW_BTREE_BUILD_STATS</varname> (<type>boolean</type>)</term>
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
