Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 9d6469c

Browse files
committed
Add a note about SystemTap vs DTrace spelling of probe names.
1 parent df858fe commit 9d6469c

File tree

1 file changed

+13
-1
lines changed

1 file changed

+13
-1
lines changed

doc/src/sgml/monitoring.sgml

+13-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.70 2009/06/17 21:58:49 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.71 2009/06/26 22:08:17 tgl Exp $ -->
22

33
<chapter id="monitoring">
44
<title>Monitoring Database Activity</title>
@@ -1568,6 +1568,17 @@ Commit 70
15681568
Total time (ns) 2312105013
15691569
</screen>
15701570
</para>
1571+
1572+
<note>
1573+
<para>
1574+
SystemTap uses a different notation for trace scripts than DTrace does,
1575+
even though the underlying trace points are compatible. One point worth
1576+
noting is that at this writing, SystemTap scripts must reference probe
1577+
names using double underlines in place of hyphens. This is expected to
1578+
be fixed in future SystemTap releases.
1579+
</para>
1580+
</note>
1581+
15711582
<para>
15721583
You should remember that DTrace scripts need to be carefully written and
15731584
debugged, otherwise the trace information collected might
@@ -1576,6 +1587,7 @@ Total time (ns) 2312105013
15761587
discussing information found using dynamic tracing, be sure to enclose
15771588
the script used to allow that too to be checked and discussed.
15781589
</para>
1590+
15791591
<para>
15801592
More example scripts can be found in the PgFoundry
15811593
<ulink url="http://pgfoundry.org/projects/dtrace/">dtrace project</ulink>.

0 commit comments

Comments
 (0)