The dtrace probes documentation [1] spells each probe name with dashes
("transaction-start", "transaction-commit", etc.). Yet as far as I can see,
dtrace only works if you spell the probe names with double underscores
("transaction__start", "transaction__commit", etc.). Why the discrepancy?
Obvious patch attached, in case this needs to be changed.
- Josh / eggyknap
1: http://www.postgresql.org/docs/8.4/static/dynamic-trace.html
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index ea8b017..672a1fe 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -1070,95 +1070,95 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS procpid,
- transaction-start
+ transaction__start
(LocalTransactionId)
Probe that fires at the start of a new transaction.
arg0 is the transaction id.
- transaction-commit
+ transaction__commit
(LocalTransactionId)
Probe that fires when a transaction completes successfully.
arg0 is the transaction id.
- transaction-abort
+ transaction__abort
(LocalTransactionId)
Probe that fires when a transaction completes unsuccessfully.
arg0 is the transaction id.
- query-start
+ query__start
(const char *)
Probe that fires when the processing of a query is started.
arg0 is the query string.
- query-done
+ query__done
(const char *)
Probe that fires when the processing of a query is complete.
arg0 is the query string.
- query-parse-start
+ query__parse__start
(const char *)
Probe that fires when the parsing of a query is started.
arg0 is the query string.
- query-parse-done
+ query__parse__done
(const char *)
Probe that fires when the parsing of a query is complete.
arg0 is the query string.
- query-rewrite-start
+ query__rewrite__start
(const char *)
Probe that fires when the rewriting of a query is started.
arg0 is the query string.
- query-rewrite-done
+ query__rewrite__done
(const char *)
Probe that fires when the rewriting of a query is complete.
arg0 is the query string.
- query-plan-start
+ query__plan__start
()
Probe that fires when the planning of a query is started.
- query-plan-done
+ query__plan__done
()
Probe that fires when the planning of a query is complete.
- query-execute-start
+ query__execute__start
()
Probe that fires when the execution of a query is started.
- query-execute-done
+ query__execute__done
()
Probe that fires when the execution of a query is complete.
- statement-status
+ statement__status
(const char *)
Probe that fires anytime the server process updates its
pg_stat_activity.current_query status.
arg0 is the new status string.
- checkpoint-start
+ checkpoint__start
(int)
Probe that fires when a checkpoint is started.
arg0 holds the bitwise flags used to distinguish different checkpoint
types, such as shutdown, immediate or force.
- checkpoint-done
+ checkpoint__done
(int, int, int, int, int)
Probe that fires when a checkpoint is complete.
(The probes listed next fire in sequence during checkpoint processing.)
@@ -1167,20 +1167,20 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS procpid,
removed and recycled respectively.
- clog-checkpoint-start
+ clog__checkpoint__start
(bool)
Probe that fires when the CLOG portion of a checkpoint is started.
arg0 is true for normal checkpoint, false for shutdown
checkpoint.
- clog-checkpoint-done
+ clog__checkpoint__done
(bool)
Probe that fires when the CLOG portion of a checkpoint is
- complete. arg0 has the same meaning as for clog-checkpoint-start.
+ complete. arg0 has the same meaning as for
clog__checkpoint__start.
- subtrans-checkpoint-start
+ subtrans__checkpoint__start
(bool)
Probe that fires when the SUBTRANS portion of a checkpoint is
started.
@@ -1188,14 +1188,14 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS procpid,
checkpoint.
- subtrans-checkpoint-done
+ subtrans__checkpoint__done
(bool)
Probe that fires when the SUBTRANS portion of a checkpoint is
complete. arg0 has the same meaning as for
- subtrans-checkpoint-start.
+ subtrans__checkpoint__start.
- multixact-checkpoint-start
+ multixact__checkpoint__start
(bool)
Probe that fires when the MultiXact portion of a checkpoint is
started.
@@ -1203,14 +1203,14 @@ SELECT pg_stat_get_backend_pid(s.
