aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-04-29 16:23:54 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2012-04-29 16:23:54 -0400
commit309c64745ea145d7c731e1fe610631b2b84e7e88 (patch)
tree1cb6c555a67cfd5d515db4c6516d3e6e7529c96c /doc/src
parent5f2b0893871cce1ffb77ac7f13b3fba227e6f11f (diff)
downloadpostgresql-309c64745ea145d7c731e1fe610631b2b84e7e88.tar.gz
postgresql-309c64745ea145d7c731e1fe610631b2b84e7e88.zip
Rename track_iotiming GUC to track_io_timing.
This spelling seems significantly more readable to me.
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml9
-rw-r--r--doc/src/sgml/monitoring.sgml2
-rw-r--r--doc/src/sgml/pgstatstatements.sgml4
3 files changed, 8 insertions, 7 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 4728ca5cf46..e58dc18df35 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -4288,10 +4288,10 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</listitem>
</varlistentry>
- <varlistentry id="guc-track-iotiming" xreflabel="track_iotiming">
- <term><varname>track_iotiming</varname> (<type>boolean</type>)</term>
+ <varlistentry id="guc-track-io-timing" xreflabel="track_io_timing">
+ <term><varname>track_io_timing</varname> (<type>boolean</type>)</term>
<indexterm>
- <primary><varname>track_iotiming</> configuration parameter</primary>
+ <primary><varname>track_io_timing</> configuration parameter</primary>
</indexterm>
<listitem>
<para>
@@ -4299,7 +4299,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
default, because it will repeatedly query the operating system for
the current time, which may cause significant overhead on some
platforms. You can use the <xref linkend="pgtesttiming"> tool to
- measure the overhead of timing on your system. Timing information is
+ measure the overhead of timing on your system.
+ I/O timing information is
displayed in <xref linkend="pg-stat-database-view">, in the output of
<xref linkend="sql-explain"> when the <literal>BUFFERS</> option is
used, and by <xref linkend="pgstatstatements">. Only superusers can
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 8378f039ff2..c9e75e4f6f9 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -155,7 +155,7 @@ postgres: <replaceable>user</> <replaceable>database</> <replaceable>host</> <re
</para>
<para>
- The parameter <xref linkend="guc-track-iotiming"> enables monitoring
+ The parameter <xref linkend="guc-track-io-timing"> enables monitoring
of block read and write times.
</para>
diff --git a/doc/src/sgml/pgstatstatements.sgml b/doc/src/sgml/pgstatstatements.sgml
index 1dd42de7815..622018e382e 100644
--- a/doc/src/sgml/pgstatstatements.sgml
+++ b/doc/src/sgml/pgstatstatements.sgml
@@ -161,7 +161,7 @@
<entry></entry>
<entry>
Total time the statement spent reading blocks, in milliseconds
- (if <xref linkend="guc-track-iotiming"> is enabled, otherwise zero)
+ (if <xref linkend="guc-track-io-timing"> is enabled, otherwise zero)
</entry>
</row>
@@ -171,7 +171,7 @@
<entry></entry>
<entry>
Total time the statement spent writing blocks, in milliseconds
- (if <xref linkend="guc-track-iotiming"> is enabled, otherwise zero)
+ (if <xref linkend="guc-track-io-timing"> is enabled, otherwise zero)
</entry>
</row>