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-8ac622ed0...@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(-)