From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Show WAL write and fsync stats in pg_stat_io |
Date: | 2023-12-01 08:30:08 |
Message-ID: | CAN55FZ3Vewh4vteM6961gR1nEKi9VdWO-NXfz90LV+otAAx+qA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Wed, 8 Nov 2023 at 10:34, Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> Is there any plan to account for WAL read stats in the WALRead()
> function which will cover walsenders i.e. WAL read by logical and
> streaming replication, WAL read by pg_walinspect and so on? I see the
> patch already covers WAL read stats by recovery in XLogPageRead(), but
> not other page_read callbacks which will end up in WALRead()
> eventually. If added, the feature at
> https://www.postgresql.org/message-id/CALj2ACXKKK%3DwbiG5_t6dGao5GoecMwRkhr7GjVBM_jg54%2BNa%3DQ%40mail.gmail.com
> can then extend it to cover WAL read from WAL buffer stats.
Yes, I am planning to create a patch for that after this patch is
done. Thanks for informing!
--
Regards,
Nazir Bilal Yavuz
Microsoft
From | Date | Subject | |
---|---|---|---|
Next Message | Wirch, Eduard | 2023-12-01 08:55:34 | Re: PostgreSql: Canceled on conflict out to old pivot |
Previous Message | li jie | 2023-12-01 08:25:17 | Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding |