rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update documentation to match pg_stat_activity changes.

This commit is contained in:
Tom Lane 2010-04-26 19:56:55 +00:00
parent 132c40424a
commit 3456cf1831
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/src/sgml/monitoring.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.79 2010/04/15 20:56:13 petere Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.80 2010/04/26 19:56:55 tgl Exp $ -->
<chapter id="monitoring"> <chapter id="monitoring">
<title>Monitoring Database Activity</title> <title>Monitoring Database Activity</title>
@ -50,7 +50,7 @@
$ ps auxww | grep ^postgres $ ps auxww | grep ^postgres
postgres 960 0.0 1.1 6104 1480 pts/1 SN 13:17 0:00 postgres -i postgres 960 0.0 1.1 6104 1480 pts/1 SN 13:17 0:00 postgres -i
postgres 963 0.0 1.1 7084 1472 pts/1 SN 13:17 0:00 postgres: writer process postgres 963 0.0 1.1 7084 1472 pts/1 SN 13:17 0:00 postgres: writer process
postgres 965 0.0 1.1 6152 1512 pts/1 SN 13:17 0:00 postgres: stats collector process postgres 965 0.0 1.1 6152 1512 pts/1 SN 13:17 0:00 postgres: stats collector process
postgres 998 0.0 2.3 6532 2992 pts/1 SN 13:18 0:00 postgres: tgl runbug 127.0.0.1 idle postgres 998 0.0 2.3 6532 2992 pts/1 SN 13:18 0:00 postgres: tgl runbug 127.0.0.1 idle
postgres 1003 0.0 2.4 6532 3128 pts/1 SN 13:19 0:00 postgres: tgl regression [local] SELECT waiting postgres 1003 0.0 2.4 6532 3128 pts/1 SN 13:19 0:00 postgres: tgl regression [local] SELECT waiting
postgres 1016 0.1 2.4 6532 3080 pts/1 SN 13:19 0:00 postgres: tgl regression [local] idle in transaction postgres 1016 0.1 2.4 6532 3080 pts/1 SN 13:19 0:00 postgres: tgl regression [local] idle in transaction
@ -165,7 +165,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
</para> </para>
<para> <para>
The statistics collector communicates with the backends needing The statistics collector communicates with the backends needing
information (including autovacuum) through temporary files. information (including autovacuum) through temporary files.
These files are stored in the <filename>pg_stat_tmp</filename> subdirectory. These files are stored in the <filename>pg_stat_tmp</filename> subdirectory.
When the postmaster shuts down, a permanent copy of the statistics When the postmaster shuts down, a permanent copy of the statistics
@ -235,9 +235,9 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
<entry><structname>pg_stat_activity</></entry> <entry><structname>pg_stat_activity</></entry>
<entry>One row per server process, showing database OID, database <entry>One row per server process, showing database OID, database
name, process <acronym>ID</>, user OID, user name, application name, name, process <acronym>ID</>, user OID, user name, application name,
current query, query's waiting status, time at which the current client's address and port number, times at which the server process,
transaction and current query began execution, time at which the current transaction, and current query began execution, process's waiting
process was started, and client's address and port number. status, and text of the current query.
The columns that report data on the current query are available unless The columns that report data on the current query are available unless
the parameter <varname>track_activities</varname> has been turned off. the parameter <varname>track_activities</varname> has been turned off.
Furthermore, these columns are only visible if the user examining Furthermore, these columns are only visible if the user examining
@ -408,7 +408,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
Beginning in <productname>PostgreSQL</productname> 8.1, indexes can be Beginning in <productname>PostgreSQL</productname> 8.1, indexes can be
used either directly or via <quote>bitmap scans</>. In a bitmap scan used either directly or via <quote>bitmap scans</>. In a bitmap scan
the output of several indexes can be combined via AND or OR rules; the output of several indexes can be combined via AND or OR rules;
so it is difficult to associate individual heap row fetches so it is difficult to associate individual heap row fetches
with specific indexes when a bitmap scan is used. Therefore, a bitmap with specific indexes when a bitmap scan is used. Therefore, a bitmap
scan increments the scan increments the
<structname>pg_stat_all_indexes</>.<structfield>idx_tup_read</> <structname>pg_stat_all_indexes</>.<structfield>idx_tup_read</>
@ -695,7 +695,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
<entry> <entry>
Returns a record of information about the backend with the specified pid, or Returns a record of information about the backend with the specified pid, or
one record for each active backend in the system if <symbol>NULL</symbol> is one record for each active backend in the system if <symbol>NULL</symbol> is
specified. The fields returned are the same as in the specified. The fields returned are a subset of those in the
<structname>pg_stat_activity</structname> view. <structname>pg_stat_activity</structname> view.
</entry> </entry>
</row> </row>