public inbox for [email protected]
help / color / mirror / Atom feedFrom: Egor Rogov <[email protected]>
To: [email protected]
Subject: Re: Suspicious description of track_io_timing
Date: Sun, 12 Jun 2016 13:03:51 -0700 (MST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
Alexander Law wrote
> The following documentation comment has been logged on the website:
>
> Page:
> https://www.postgresql.org/docs/9.6/static/runtime-config-statistics.html
> Description:
>
> There is the following sentence in description of the track_io_timing
> parameter:
>
> 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">.
>
> Is it correct? Shouldn't the TIMING option be mentioned there instead
> of
> BUFFERS?
Yes, it's correct. Track_io_timing parameter corresponds to the buffer
manager. With BUFFERS option EXPLAIN shows buffers usage; when
track_io_timing is on it also shows I/O read and write time.
Egor Rogov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
View this message in context: http://postgresql.nabble.com/Suspicious-description-of-track-io-timing-tp5905853p5907482.html
Sent from the PostgreSQL - docs mailing list archive at Nabble.com.
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Suspicious description of track_io_timing
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox