Re: Doc: fix track_io_timing description to mention pg_stat_io

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Hajime(dot)Matsunaga(at)nttdata(dot)com, byavuz81(at)gmail(dot)com, melanieplageman(at)gmail(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Masao(dot)Fujii(at)nttdata(dot)com
Subject: Re: Doc: fix track_io_timing description to mention pg_stat_io
Date: 2024-07-03 10:43:40
Message-ID: 8412d293-9a2a-4b06-80c2-b745f3bdceac@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024/07/03 17:51, Hajime(dot)Matsunaga(at)nttdata(dot)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.

Regards,

--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-07-03 11:02:12 Re: speed up a logical replica setup
Previous Message Dilip Kumar 2024-07-03 10:42:12 Re: Conflict Detection and Resolution