RE: Doc: fix track_io_timing description to mention pg_stat_io - Mailing list pgsql-hackers

From
Subject RE: Doc: fix track_io_timing description to mention pg_stat_io
Date
Msg-id TYWPR01MB1074289CA6F9E0228247EF31CA4DA2@TYWPR01MB10742.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Doc: fix track_io_timing description to mention pg_stat_io  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Doc: fix track_io_timing description to mention pg_stat_io
List pgsql-hackers

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.


Regards,
--
Hajime Matsunaga
NTT DATA Group Corporation


Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Interrupts vs signals
Next
From: Amit Kapila
Date:
Subject: Re: walsender.c comment with no context is hard to understand