Re: Restrict data checksums entries in pg_stat_io
От
Daniel Gustafsson
Тема
Re: Restrict data checksums entries in pg_stat_io
Дата
Msg-id
54EEF31B-3487-45F4-84B8-9F177347ED4B@yesql.se
Ответ на
Re: Restrict data checksums entries in pg_stat_io (Fujii Masao)
Список
Дерево обсуждения
Restrict data checksums entries in pg_stat_io Fujii Masao <masao.fujii@gmail.com>
Re: Restrict data checksums entries in pg_stat_io Daniel Gustafsson <daniel@yesql.se>
Re: Restrict data checksums entries in pg_stat_io Fujii Masao <masao.fujii@gmail.com>
Re: Restrict data checksums entries in pg_stat_io Daniel Gustafsson <daniel@yesql.se>
Re: Restrict data checksums entries in pg_stat_io Fujii Masao <masao.fujii@gmail.com>
> On 16 Jul 2026, at 19:13, Fujii Masao 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 по дате отправления