Re: Doc: fix track_io_timing description to mention pg_stat_io
Fujii Masao <masao.fujii@oss.nttdata.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Hajime.Matsunaga@nttdata.com, byavuz81@gmail.com,
melanieplageman@gmail.com
Cc: pgsql-hackers@lists.postgresql.org, Masao.Fujii@nttdata.com
Date: 2024-07-10T07:02:32Z
Lists: pgsql-hackers
On 2024/07/08 12:01, Hajime.Matsunaga@nttdata.com wrote: > > > From: Fujii Masao <masao.fujii@oss.nttdata.com> > Sent: Wednesday, July 3, 2024 7:44 PM >> >> On 2024/07/03 17:51, Hajime.Matsunaga@nttdata.com wrote: >>> Thanks for the suggestions the other day. >>> I have created a patch that incorporates your suggestions. >> >> - <structname>pg_stat_database</structname></link>, in the output of >> + <structname>pg_stat_database</structname></link> and >> + <link linkend="monitoring-pg-stat-io-view"> >> + <structname>pg_stat_io</structname></link>, in the output of >> >> I'm not a native English speaker, but it seems more natural to use a comma instead of "and" before "pg_stat_io." >> >> - of block read and write times. >> + of block read, block write, extend, and fsync times. >> >> "block" before "fsync" doesn't seem necessary. > > I'm also not a native English speaker, so I appreciate your feedback. > I have created a patch that incorporates your feedback. Thanks for updating the patch! Pushed. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION
Commits
-
doc: Update track_io_timing documentation to mention pg_stat_io.
- 0d483ad4cc4c 16.4 landed
- 0248762b2a8e 17.0 landed
- 05506510de6a 18.0 landed