From: Andres Freund <andres@anarazel.de>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: bufmgr: Remove buffer-write-dirty tracepoints
Date: Tue, 04 Apr 2023 01:19:19 +0000
Message-ID: <E1pjVKQ-001FGl-Mk@gemulon.postgresql.org> (raw)
bufmgr: Remove buffer-write-dirty tracepoints
The trace point was using the relfileno / fork / block for the to-be-read-in
buffer. Some upcoming work would make that more expensive to provide. We still
have buffer-flush-start/done, which can serve most tracing needs that
buffer-write-dirty could serve.
Discussion: https://postgr.es/m/f5164e7a-eef6-8972-75a3-8ac622ed0c6e@iki.fi
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/8a2b1b147728b11f6df569081d121b9e3135109d
Modified Files
--------------
doc/src/sgml/monitoring.sgml | 17 -----------------
src/backend/storage/buffer/bufmgr.c | 10 ----------
src/backend/utils/probes.d | 2 --
3 files changed, 29 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: andres@anarazel.de, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: bufmgr: Remove buffer-write-dirty tracepoints
In-Reply-To: <E1pjVKQ-001FGl-Mk@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox