1- <!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.78 2010/04/15 20:48:22 petere Exp $ -->
1+ <!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.79 2010/04/15 20:56:13 petere Exp $ -->
22
33<chapter id="monitoring">
44 <title>Monitoring Database Activity</title>
@@ -487,15 +487,15 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
487487 <entry><literal><function>pg_stat_get_db_xact_commit</function>(<type>oid</type>)</literal></entry>
488488 <entry><type>bigint</type></entry>
489489 <entry>
490- Transactions committed in database
490+ Number of transactions committed in database
491491 </entry>
492492 </row>
493493
494494 <row>
495495 <entry><literal><function>pg_stat_get_db_xact_rollback</function>(<type>oid</type>)</literal></entry>
496496 <entry><type>bigint</type></entry>
497497 <entry>
498- Transactions rolled back in database
498+ Number of transactions rolled back in database
499499 </entry>
500500 </row>
501501
@@ -696,15 +696,15 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
696696 Returns a record of information about the backend with the specified pid, or
697697 one record for each active backend in the system if <symbol>NULL</symbol> is
698698 specified. The fields returned are the same as in the
699- <structname>pg_stat_activity</structname> view
699+ <structname>pg_stat_activity</structname> view.
700700 </entry>
701701 </row>
702702
703703 <row>
704704 <entry><literal><function>pg_stat_get_function_calls</function>(<type>oid</type>)</literal></entry>
705705 <entry><type>bigint</type></entry>
706706 <entry>
707- Number of times the function has been called.
707+ Number of times the function has been called
708708 </entry>
709709 </row>
710710
@@ -731,7 +731,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
731731 <entry><type>setof integer</type></entry>
732732 <entry>
733733 Set of currently active server process numbers (from 1 to the
734- number of active server processes). See usage example in the text
734+ number of active server processes). See usage example in the text.
735735 </entry>
736736 </row>
737737
@@ -820,8 +820,8 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
820820 <entry><type>inet</type></entry>
821821 <entry>
822822 The IP address of the client connected to the given
823- server process. Null if the connection is over a Unix domain
824- socket. Also null if the current user is not a superuser nor
823+ server process; null if the connection is over a Unix domain
824+ socket, also null if the current user is not a superuser nor
825825 the same user as that of the session being queried
826826 </entry>
827827 </row>
@@ -831,8 +831,8 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
831831 <entry><type>integer</type></entry>
832832 <entry>
833833 The TCP port number of the client connected to the given
834- server process. -1 if the connection is over a Unix domain
835- socket. Null if the current user is not a superuser nor the
834+ server process; -1 if the connection is over a Unix domain
835+ socket, null if the current user is not a superuser nor the
836836 same user as that of the session being queried
837837 </entry>
838838 </row>
@@ -841,7 +841,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
841841 <entry><literal><function>pg_stat_get_bgwriter_timed_checkpoints</function>()</literal></entry>
842842 <entry><type>bigint</type></entry>
843843 <entry>
844- The number of times the background writer has started timed checkpoints
844+ Number of times the background writer has started timed checkpoints
845845 (because the <varname>checkpoint_timeout</varname> time has expired)
846846 </entry>
847847 </row>
@@ -850,7 +850,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
850850 <entry><literal><function>pg_stat_get_bgwriter_requested_checkpoints</function>()</literal></entry>
851851 <entry><type>bigint</type></entry>
852852 <entry>
853- The number of times the background writer has started checkpoints based
853+ Number of times the background writer has started checkpoints based
854854 on requests from backends because the <varname>checkpoint_segments</varname>
855855 has been exceeded or because the <command>CHECKPOINT</command>
856856 command has been issued
@@ -861,15 +861,15 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
861861 <entry><literal><function>pg_stat_get_bgwriter_buf_written_checkpoints</function>()</literal></entry>
862862 <entry><type>bigint</type></entry>
863863 <entry>
864- The number of buffers written by the background writer during checkpoints
864+ Number of buffers written by the background writer during checkpoints
865865 </entry>
866866 </row>
867867
868868 <row>
869869 <entry><literal><function>pg_stat_get_bgwriter_buf_written_clean</function>()</literal></entry>
870870 <entry><type>bigint</type></entry>
871871 <entry>
872- The number of buffers written by the background writer for routine cleaning of
872+ Number of buffers written by the background writer for routine cleaning of
873873 dirty pages
874874 </entry>
875875 </row>
@@ -878,7 +878,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
878878 <entry><literal><function>pg_stat_get_bgwriter_maxwritten_clean</function>()</literal></entry>
879879 <entry><type>bigint</type></entry>
880880 <entry>
881- The number of times the background writer has stopped its cleaning scan because
881+ Number of times the background writer has stopped its cleaning scan because
882882 it has written more buffers than specified in the
883883 <varname>bgwriter_lru_maxpages</varname> parameter
884884 </entry>
@@ -888,7 +888,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
888888 <entry><literal><function>pg_stat_get_buf_written_backend</function>()</literal></entry>
889889 <entry><type>bigint</type></entry>
890890 <entry>
891- The number of buffers written by backends because they needed
891+ Number of buffers written by backends because they needed
892892 to allocate a new buffer
893893 </entry>
894894 </row>
@@ -897,7 +897,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
897897 <entry><literal><function>pg_stat_get_buf_alloc</function>()</literal></entry>
898898 <entry><type>bigint</type></entry>
899899 <entry>
900- The total number of buffer allocations
900+ Total number of buffer allocations
901901 </entry>
902902 </row>
903903
@@ -1101,19 +1101,19 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS procpid,
11011101 <entry>transaction-start</entry>
11021102 <entry>(LocalTransactionId)</entry>
11031103 <entry>Probe that fires at the start of a new transaction.
1104- arg0 is the transactionid .</entry>
1104+ arg0 is the transactionID .</entry>
11051105 </row>
11061106 <row>
11071107 <entry>transaction-commit</entry>
11081108 <entry>(LocalTransactionId)</entry>
11091109 <entry>Probe that fires when a transaction completes successfully.
1110- arg0 is the transactionid .</entry>
1110+ arg0 is the transactionID .</entry>
11111111 </row>
11121112 <row>
11131113 <entry>transaction-abort</entry>
11141114 <entry>(LocalTransactionId)</entry>
11151115 <entry>Probe that fires when a transaction completes unsuccessfully.
1116- arg0 is the transactionid .</entry>
1116+ arg0 is the transactionID .</entry>
11171117 </row>
11181118 <row>
11191119 <entry>query-start</entry>