agora inbox for pgsql-committers@postgresql.orghelp / color / mirror / Atom feed
pgsql: Restrict pg_stat_io entries for data checksum processes 2+ messages / 1 participants [nested] [flat]
* pgsql: Restrict pg_stat_io entries for data checksum processes @ 2026-07-17 11:18 Fujii Masao <fujii@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-07-17 11:18 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Restrict pg_stat_io entries for data checksum processes The data checksums launcher and workers were exposed in pg_stat_io with the same broad set of object/context combinations as general background workers. However, several of those entries can never accumulate I/O statistics for these processes, such as bulkwrite, relation init, temporary relation, and launcher vacuum entries. Teach pgstat_tracks_io_object() and pgstat_tracks_io_op() about the actual I/O performed by the data checksum processes. Keep the entries needed for catalog scans, including bulkread catalog scans, worker relation processing with a vacuum access strategy, and WAL writes and initialization, while excluding WAL reads and other object/context combinations that can never be used. Author: Fujii Masao <masao.fujii@gmail.com> Reviewed-by: Daniel Gustafsson <daniel@yesql.se> Discussion: https://postgr.es/m/CAHGQGwHz_-nt+YkHDMRZNBZrnoHro8cMOgSwuXEmSYT6vxgQ=w@mail.gmail.com Backpatch-through: 19 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/32e4508db27d1fa3dc07404ad69d43ed97870f15 Modified Files -------------- src/backend/utils/activity/pgstat_io.c | 33 +++++++++++++++++++++++++++++++++ src/test/regress/expected/stats.out | 9 +-------- 2 files changed, 34 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Restrict pg_stat_io entries for data checksum processes @ 2026-07-17 11:18 Fujii Masao <fujii@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-07-17 11:18 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org Restrict pg_stat_io entries for data checksum processes The data checksums launcher and workers were exposed in pg_stat_io with the same broad set of object/context combinations as general background workers. However, several of those entries can never accumulate I/O statistics for these processes, such as bulkwrite, relation init, temporary relation, and launcher vacuum entries. Teach pgstat_tracks_io_object() and pgstat_tracks_io_op() about the actual I/O performed by the data checksum processes. Keep the entries needed for catalog scans, including bulkread catalog scans, worker relation processing with a vacuum access strategy, and WAL writes and initialization, while excluding WAL reads and other object/context combinations that can never be used. Author: Fujii Masao <masao.fujii@gmail.com> Reviewed-by: Daniel Gustafsson <daniel@yesql.se> Discussion: https://postgr.es/m/CAHGQGwHz_-nt+YkHDMRZNBZrnoHro8cMOgSwuXEmSYT6vxgQ=w@mail.gmail.com Backpatch-through: 19 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/3aa54433b0cdce48facb610a5b720208cc760654 Modified Files -------------- src/backend/utils/activity/pgstat_io.c | 33 +++++++++++++++++++++++++++++++++ src/test/regress/expected/stats.out | 9 +-------- 2 files changed, 34 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-07-17 11:18 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-07-17 11:18 pgsql: Restrict pg_stat_io entries for data checksum processes Fujii Masao <fujii@postgresql.org> 2026-07-17 11:18 pgsql: Restrict pg_stat_io entries for data checksum processes Fujii Masao <fujii@postgresql.org>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox