Re: Restrict data checksums entries in pg_stat_io

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Restrict data checksums entries in pg_stat_io
Date: 2026-07-17 08:12:27
Message-ID: 54EEF31B-3487-45F4-84B8-9F177347ED4B@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 16 Jul 2026, at 19:13, Fujii Masao <masao(dot)fujii(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message wenhui qiu 2026-07-17 08:17:02 Re: PGLZ Compression Optimization
Previous Message Peter Smith 2026-07-17 08:07:27 Re: Support EXCEPT for TABLES IN SCHEMA publications