Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit48f7e64

Browse files
committed
Simplify and rename some GUC variables, per various recent discussions:
* stats_start_collector goes away; we always start the collector process,unless prevented by a problem with setting up the stats UDP socket.* stats_reset_on_server_start goes away; it seems useless in view of theavailability of pg_stat_reset().* stats_block_level and stats_row_level are merged into a single variable"track_counts", which controls all reports sent to the collector process.* stats_command_string is renamed to track_activities.* log_autovacuum is renamed to log_autovacuum_min_duration to better reflectits meaning.The log_autovacuum change is not a compatibility issue since it didn't existbefore 8.3 anyway. The other changes need to be release-noted.
1 parent0213835 commit48f7e64

File tree

14 files changed

+172
-341
lines changed

14 files changed

+172
-341
lines changed

‎doc/src/sgml/config.sgml‎

Lines changed: 38 additions & 96 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.145 2007/09/22 19:10:44 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.146 2007/09/24 03:12:23 tgl Exp $ -->
22

33
<chapter Id="runtime-config">
44
<title>Server Configuration</title>
@@ -3186,30 +3186,19 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
31863186
<title>Query and Index Statistics Collector</title>
31873187

31883188
<para>
3189-
These parameters controlaserver-wide statistics collectionfeature.
3189+
These parameters control server-wide statistics collectionfeatures.
31903190
When statistics collection is enabled, the data that is produced can be
31913191
accessed via the <structname>pg_stat</structname> and
31923192
<structname>pg_statio</structname> family of system views.
31933193
Refer to <xref linkend="monitoring"> for more information.
31943194
</para>
31953195

3196-
<note>
3197-
<para>
3198-
As of <productname>PostgreSQL</productname> 8.2,
3199-
<varname>stats_command_string</varname> controls a separate data
3200-
collection mechanism that can be turned on or off independently
3201-
of whether the statistics-collection subprocess is running.
3202-
The subprocess is only needed to support collection of
3203-
block-level or row-level statistics.
3204-
</para>
3205-
</note>
3206-
32073196
<variablelist>
32083197

3209-
<varlistentry id="guc-stats-command-string" xreflabel="stats_command_string">
3210-
<term><varname>stats_command_string</varname> (<type>boolean</type>)</term>
3198+
<varlistentry id="guc-track-activities" xreflabel="track_activities">
3199+
<term><varname>track_activities</varname> (<type>boolean</type>)</term>
32113200
<indexterm>
3212-
<primary><varname>stats_command_string</> configuration parameter</primary>
3201+
<primary><varname>track_activities</> configuration parameter</primary>
32133202
</indexterm>
32143203
<listitem>
32153204
<para>
@@ -3225,80 +3214,33 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
32253214
</listitem>
32263215
</varlistentry>
32273216

3228-
<varlistentry id="guc-update-process-title" xreflabel="update_process_title">
3229-
<term><varname>update_process_title</varname> (<type>boolean</type>)</term>
3230-
<indexterm>
3231-
<primary><varname>update_process_title</> configuration parameter</primary>
3232-
</indexterm>
3233-
<listitem>
3234-
<para>
3235-
Enables updating of the process title every time a new SQL command
3236-
is received by the server. The process title is typically viewed
3237-
by the <command>ps</> command or in Windows using the <application>Process
3238-
Explorer</>. Only superusers can change this setting.
3239-
</para>
3240-
</listitem>
3241-
</varlistentry>
3242-
3243-
<varlistentry id="guc-stats-start-collector" xreflabel="stats_start_collector">
3244-
<term><varname>stats_start_collector</varname> (<type>boolean</type>)</term>
3245-
<indexterm>
3246-
<primary><varname>stats_start_collector</> configuration parameter</primary>
3247-
</indexterm>
3248-
<listitem>
3249-
<para>
3250-
Controls whether the server should start the
3251-
statistics-collection subprocess. This is on by default, but
3252-
can be turned off if you know you have no interest in
3253-
collecting statistics or running autovacuum.
3254-
This parameter can only be set at server start, because the collection
3255-
subprocess cannot be started or stopped on-the-fly. (However, the
3256-
extent to which statistics are actually gathered can be changed while
3257-
the server is running, so long as the subprocess exists.)
3258-
</para>
3259-
</listitem>
3260-
</varlistentry>
3261-
3262-
<varlistentry id="guc-stats-block-level" xreflabel="stats_block_level">
3263-
<term><varname>stats_block_level</varname> (<type>boolean</type>)</term>
3264-
<indexterm>
3265-
<primary><varname>stats_block_level</> configuration parameter</primary>
3266-
</indexterm>
3267-
<listitem>
3268-
<para>
3269-
Enables the collection of block-level statistics on database
3270-
activity. This parameter is off by default.
3271-
Only superusers can change this setting.
3272-
</para>
3273-
</listitem>
3274-
</varlistentry>
3275-
3276-
<varlistentry id="guc-stats-row-level" xreflabel="stats_row_level">
3277-
<term><varname>stats_row_level</varname> (<type>boolean</type>)</term>
3217+
<varlistentry id="guc-track-counts" xreflabel="track_counts">
3218+
<term><varname>track_counts</varname> (<type>boolean</type>)</term>
32783219
<indexterm>
3279-
<primary><varname>stats_row_level</> configuration parameter</primary>
3220+
<primary><varname>track_counts</> configuration parameter</primary>
32803221
</indexterm>
32813222
<listitem>
32823223
<para>
3283-
Enablesthecollection ofrow-levelstatistics on database
3284-
activity.This parameter is on by default, because the autovacuum
3224+
Enables collection of statistics on database activity.
3225+
This parameter is on by default, because the autovacuum
32853226
daemon needs the collected information.
32863227
Only superusers can change this setting.
32873228
</para>
32883229
</listitem>
32893230
</varlistentry>
32903231

3291-
<varlistentry id="guc-stats-reset-on-server-start" xreflabel="stats_reset_on_server_start">
3292-
<term><varname>stats_reset_on_server_start</varname> (<type>boolean</type>)</term>
3232+
<varlistentry id="guc-update-process-title" xreflabel="update_process_title">
3233+
<term><varname>update_process_title</varname> (<type>boolean</type>)</term>
32933234
<indexterm>
3294-
<primary><varname>stats_reset_on_server_start</> configuration parameter</primary>
3235+
<primary><varname>update_process_title</> configuration parameter</primary>
32953236
</indexterm>
32963237
<listitem>
32973238
<para>
3298-
If on, collected block-level and row-level statistics are zeroed out
3299-
whenever the server is restarted. If off, statistics are accumulated
3300-
across server restarts. This parameter is off by default.
3301-
This parameter can only be set at server start.
3239+
Enables updating of the process title every time a new SQL command
3240+
is received by the server. The process title is typically viewed
3241+
by the <command>ps</> command,
3242+
or in Windows by using the <application>Process Explorer</>.
3243+
Only superusers can change this setting.
33023244
</para>
33033245
</listitem>
33043246
</varlistentry>
@@ -3369,50 +3311,50 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
33693311
<listitem>
33703312
<para>
33713313
Controls whether the server should run the
3372-
autovacuum launcher daemon. This is on by default.
3373-
<varname>stats_start_collector</> and <varname>stats_row_level</>
3374-
must also be turned on forautovacuum to work.
3314+
autovacuum launcher daemon. This is on by default; however,
3315+
<xref linkend="guc-track-counts"> must also be turned on for
3316+
autovacuum to work.
33753317
This parameter can only be set in the <filename>postgresql.conf</>
33763318
file or on the server command line.
33773319
</para>
33783320
<para>
33793321
Note that even when this parameter is disabled, the system
3380-
willperiodicallylaunch autovacuum processesin order to
3322+
will launch autovacuum processesif necessary to
33813323
prevent transaction ID wraparound. See <xref
33823324
linkend="vacuum-for-wraparound"> for more information.
33833325
</para>
33843326
</listitem>
33853327
</varlistentry>
33863328

3387-
<varlistentry id="guc-autovacuum-max-workers" xreflabel="autovacuum_max_workers">
3388-
<term><varname>autovacuum_max_workers</varname> (<type>integer</type>)</term>
3329+
<varlistentry id="guc-log-autovacuum-min-duration" xreflabel="log_autovacuum_min_duration">
3330+
<term><varname>log_autovacuum_min_duration</varname> (<type>integer</type>)</term>
33893331
<indexterm>
3390-
<primary><varname>autovacuum_max_workers</> configuration parameter</primary>
3332+
<primary><varname>log_autovacuum_min_duration</> configuration parameter</primary>
33913333
</indexterm>
33923334
<listitem>
33933335
<para>
3394-
Specifies the maximum number of autovacuum processes (other than the
3395-
autovacuum launcher) which may be running at any one time. The default
3396-
is three (<literal>3</literal>). This parameter can only be set in
3336+
Causes each action executed by autovacuum to be logged if it ran for at
3337+
least the specified number of milliseconds. Setting this to zero logs
3338+
all autovacuum actions. Minus-one (the default) disables logging
3339+
autovacuum actions. For example, if you set this to
3340+
<literal>250ms</literal> then all automatic vacuums and analyzes that run
3341+
250ms or longer will be logged. Enabling this parameter can be helpful
3342+
in tracking autovacuum activity. This setting can only be set in
33973343
the <filename>postgresql.conf</> file or on the server command line.
33983344
</para>
33993345
</listitem>
34003346
</varlistentry>
34013347

3402-
<varlistentry id="guc-log-autovacuum" xreflabel="log_autovacuum">
3403-
<term><varname>log_autovacuum</varname> (<type>integer</type>)</term>
3348+
<varlistentry id="guc-autovacuum-max-workers" xreflabel="autovacuum_max_workers">
3349+
<term><varname>autovacuum_max_workers</varname> (<type>integer</type>)</term>
34043350
<indexterm>
3405-
<primary><varname>log_autovacuum</> configuration parameter</primary>
3351+
<primary><varname>autovacuum_max_workers</> configuration parameter</primary>
34063352
</indexterm>
34073353
<listitem>
34083354
<para>
3409-
Causes each action executed by autovacuum to be logged if it ran for at
3410-
least the specified number of milliseconds. Setting this to zero logs
3411-
all autovacuum actions. Minus-one (the default) disables logging
3412-
autovacuum actions. For example, if you set this to
3413-
<literal>250ms</literal> then all vacuums and analyzes that run
3414-
250ms or longer will be logged. Enabling this parameter can be helpful
3415-
in tracking autovacuum activity. This setting can only be set in
3355+
Specifies the maximum number of autovacuum processes (other than the
3356+
autovacuum launcher) which may be running at any one time. The default
3357+
is three. This parameter can only be set in
34163358
the <filename>postgresql.conf</> file or on the server command line.
34173359
</para>
34183360
</listitem>

‎doc/src/sgml/maintenance.sgml‎

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.81 2007/09/14 13:43:03 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.82 2007/09/24 03:12:23 tgl Exp $ -->
22

33
<chapter id="maintenance">
44
<title>Routine Database Maintenance Tasks</title>
@@ -203,7 +203,7 @@
203203
</sect2>
204204

205205
<sect2 id="vacuum-for-statistics">
206-
<title>Updatingplanner statistics</title>
206+
<title>UpdatingPlanner Statistics</title>
207207

208208
<indexterm zone="vacuum-for-statistics">
209209
<primary>statistics</primary>
@@ -279,7 +279,7 @@
279279
</sect2>
280280

281281
<sect2 id="vacuum-for-wraparound">
282-
<title>Preventingtransaction IDwraparound failures</title>
282+
<title>PreventingTransaction IDWraparound Failures</title>
283283

284284
<indexterm zone="vacuum-for-wraparound">
285285
<primary>transaction ID</primary>
@@ -460,7 +460,7 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
460460
</sect2>
461461

462462
<sect2 id="autovacuum">
463-
<title id="autovacuum-title">Theauto-vacuum daemon</title>
463+
<title id="autovacuum-title">TheAuto-Vacuum Daemon</title>
464464

465465
<indexterm>
466466
<primary>autovacuum</primary>
@@ -473,10 +473,9 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
473473
<command>VACUUM</command> and <command>ANALYZE </command> commands.
474474
When enabled, autovacuum checks for
475475
tables that have had a large number of inserted, updated or deleted
476-
tuples. These checks use therow-levelstatistics collection facility;
476+
tuples. These checks use the statistics collection facility;
477477
therefore, autovacuum cannot be used unless <xref
478-
linkend="guc-stats-start-collector"> and <xref
479-
linkend="guc-stats-row-level"> are set to <literal>true</literal>.
478+
linkend="guc-track-counts"> is set to <literal>true</literal>.
480479
In the default configuration, autovacuuming is enabled and the related
481480
configuration parameters are appropriately set.
482481
</para>
@@ -497,8 +496,8 @@ HINT: Stop the postmaster and use a standalone backend to VACUUM in "mydb".
497496
eligible for vacuuming in a short amount of time, all autovacuum workers
498497
may end up vacuuming those tables for a very long time. This would result
499498
in other tables and databases not being vacuumed until a worker became
500-
available. There isalsonot a limit on how many workers might be in a
501-
single database, but workers do tryand avoid repeating work that has
499+
available. There is not a limit on how many workers might be in a
500+
single database, but workers do tryto avoid repeating work that has
502501
already been done by other workers. Note that the number of running
503502
workers does not count towards the <xref linkend="guc-max-connections"> nor
504503
the <xref linkend="guc-superuser-reserved-connections"> limits.

‎doc/src/sgml/monitoring.sgml‎

Lines changed: 16 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.52 2007/09/20 17:56:30 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.53 2007/09/24 03:12:23 tgl Exp $ -->
22

33
<chapter id="monitoring">
44
<title>Monitoring Database Activity</title>
@@ -117,14 +117,15 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
117117
<productname>PostgreSQL</productname>'s <firstterm>statistics collector</>
118118
is a subsystem that supports collection and reporting of information about
119119
server activity. Presently, the collector can count accesses to tables
120-
and indexes in both disk-block and individual-row terms.
120+
and indexes in both disk-block and individual-row terms. It also tracks
121+
total numbers of rows in each table, and the last vacuum and analyze times
122+
for each table.
121123
</para>
122124

123125
<para>
124126
<productname>PostgreSQL</productname> also supports determining the exact
125127
command currently being executed by other server processes. This is an
126-
independent facility that can be enabled or disabled whether or not
127-
block-level and row-level statistics are being collected.
128+
independent facility that does not depend on the collector process.
128129
</para>
129130

130131
<sect2 id="monitoring-stats-setup">
@@ -139,31 +140,14 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
139140
</para>
140141

141142
<para>
142-
The parameter <xref linkend="guc-stats-start-collector"> must be
143-
set to <literal>true</> for the statistics collector to be launched
144-
at all. This is the default and recommended setting, but it can be
145-
turned off if you have no interest in statistics and want to
146-
squeeze out every last drop of overhead. (The savings is likely to
147-
be small, however.) Note that this option cannot be changed while
148-
the server is running.
143+
The parameter <xref linkend="guc-track-counts"> controls whether
144+
information is actually sent to the collector process and thus determines
145+
whether any run-time overhead occurs for event counting.
149146
</para>
150147

151148
<para>
152-
The parameters <xref linkend="guc-stats-block-level"> and <xref
153-
linkend="guc-stats-row-level"> control how much information is
154-
actually sent to the collector and thus determine how much run-time
155-
overhead occurs. These respectively determine whether a server
156-
process tracks disk-block-level access
157-
statistics and row-level access statistics and sends these to the collector.
158-
Additionally, per-database transaction commit and abort statistics
159-
are collected if either of these parameters are set.
160-
</para>
161-
162-
<para>
163-
The parameter <xref linkend="guc-stats-command-string"> enables monitoring
149+
The parameter <xref linkend="guc-track-activities"> enables monitoring
164150
of the current command being executed by any server process.
165-
The statistics collector subprocess need not be running to enable this
166-
feature.
167151
</para>
168152

169153
<para>
@@ -190,13 +174,13 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
190174
<para>
191175
When using the statistics to monitor current activity, it is important
192176
to realize that the information does not update instantaneously.
193-
Each individual server process transmits newblock and row access counts to
177+
Each individual server process transmits newstatistical counts to
194178
the collector just before going idle; so a query or transaction still in
195179
progress does not affect the displayed totals. Also, the collector itself
196180
emits a new report at most once per <varname>PGSTAT_STAT_INTERVAL</varname>
197181
milliseconds (500 unless altered while building the server). So the
198182
displayed information lags behind actual activity. However, current-query
199-
information collected by <varname>stats_command_string</varname> is
183+
information collected by <varname>track_activities</varname> is
200184
always up-to-date.
201185
</para>
202186

@@ -240,7 +224,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
240224
current query began execution, time at which the process was
241225
started, and client's address and port number. The columns that
242226
report data on the current query are available unless the parameter
243-
<varname>stats_command_string</varname> has been turned off.
227+
<varname>track_activities</varname> has been turned off.
244228
Furthermore, these columns are only visible if the user examining
245229
the view is a superuser or the same as the user owning the process
246230
being reported on.
@@ -715,7 +699,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
715699
Active command of the given server process, but only if the
716700
current user is a superuser or the same user as that of
717701
the session being queried (and
718-
<varname>stats_command_string</varname> is on)
702+
<varname>track_activities</varname> is on)
719703
</entry>
720704
</row>
721705

@@ -726,7 +710,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
726710
True if the given server process is waiting for a lock,
727711
but only if the current user is a superuser or the same user as that of
728712
the session being queried (and
729-
<varname>stats_command_string</varname> is on)
713+
<varname>track_activities</varname> is on)
730714
</entry>
731715
</row>
732716

@@ -738,7 +722,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
738722
executing query was started, but only if the
739723
current user is a superuser or the same user as that of
740724
the session being queried (and
741-
<varname>stats_command_string</varname> is on)
725+
<varname>track_activities</varname> is on)
742726
</entry>
743727
</row>
744728

@@ -750,7 +734,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
750734
executing transaction was started, but only if the
751735
current user is a superuser or the same user as that of
752736
the session being queried (and
753-
<varname>stats_command_string</varname> is on)
737+
<varname>track_activities</varname> is on)
754738
</entry>
755739
</row>
756740

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp