Re: Restrict data checksums entries in pg_stat_io - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Restrict data checksums entries in pg_stat_io
Date
Msg-id CAHGQGwGw0_EWvACZgY2+3kikdbgS1F=NmP+vbQhD5roDE3MGDw@mail.gmail.com
Whole thread
In response to Re: Restrict data checksums entries in pg_stat_io  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On Fri, Jul 17, 2026 at 5:12 PM Daniel Gustafsson <daniel@yesql.se> wrote:
>
> > On 16 Jul 2026, at 19:13, Fujii Masao <masao.fujii@gmail.com> wrote:
>
> > Both the launcher and the worker use table_beginscan_catalog(), which
> > can select BAS_BULKREAD when scanning large catalogs, i.e., pg_database
> > for the launcher and pg_class for the worker. As a result, seems their
> > I/O can be reported under the bulkread context.
>
> Interesting, I didn't realize that any catalog read could use bulkread but it
> clearly makes sense.
>
> > So I've updated the patch to keep relation/bulkread for both data checksums
> > processes. Patch attached.
>
> +1

Thanks for the review! I've pushed the patch.

Regards,

--
Fujii Masao



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Restore check_mut_excl_opts, usage in pg_restore and pg_dumpall
Next
From: Antonin Houska
Date:
Subject: Re: Batching in executor