From 8a2b1b147728b11f6df569081d121b9e3135109d Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Mon, 3 Apr 2023 18:02:41 -0700 Subject: 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 --- doc/src/sgml/monitoring.sgml | 17 ----------------- 1 file changed, 17 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml index d5a45f996d0..65da082ed9b 100644 --- a/doc/src/sgml/monitoring.sgml +++ b/doc/src/sgml/monitoring.sgml @@ -7817,23 +7817,6 @@ FROM pg_stat_get_backend_idset() AS backendid; it's typically not actually been written to disk yet.) The arguments are the same as for buffer-flush-start. - - buffer-write-dirty-start - (ForkNumber, BlockNumber, Oid, Oid, Oid) - Probe that fires when a server process begins to write a dirty - buffer. (If this happens often, it implies that - is too - small or the background writer control parameters need adjustment.) - arg0 and arg1 contain the fork and block numbers of the page. - arg2, arg3, and arg4 contain the tablespace, database, and relation OIDs - identifying the relation. - - - buffer-write-dirty-done - (ForkNumber, BlockNumber, Oid, Oid, Oid) - Probe that fires when a dirty-buffer write is complete. - The arguments are the same as for buffer-write-dirty-start. - wal-buffer-write-dirty-start () -- cgit v1.2.3