| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: bufmgr: Remove buffer-write-dirty tracepoints |
| Date: | 2023-04-04 01:19:19 |
| Message-ID: | E1pjVKQ-001FGl-Mk@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-04-04 12:05:06 | pgsql: Code review for recent SQL/JSON commits |
| Previous Message | Peter Geoghegan | 2023-04-03 18:48:22 | pgsql: Make SP-GiST redirect cleanup more aggressive. |