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

From Daniel Gustafsson
Subject Re: Restrict data checksums entries in pg_stat_io
Date
Msg-id 54EEF31B-3487-45F4-84B8-9F177347ED4B@yesql.se
Whole thread
In response to Re: Restrict data checksums entries in pg_stat_io  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Restrict data checksums entries in pg_stat_io
List pgsql-hackers
> 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

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Support EXCEPT for TABLES IN SCHEMA publications
Next
From: wenhui qiu
Date:
Subject: Re: PGLZ Compression Optimization