index f5dce009fff35e18641a832912415bd6c0c3409d..7bd21a74b427d773208aa4cbda0aad6c38ea5049 100644 (file)
-<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.70 2009年06月17日 21:58:49 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/monitoring.sgml,v 1.71 2009年06月26日 22:08:17 tgl Exp $ -->
<chapter id="monitoring">
<title>Monitoring Database Activity</title>
Total time (ns) 2312105013
</screen>
</para>
+
+ <note>
+ <para>
+ SystemTap uses a different notation for trace scripts than DTrace does,
+ even though the underlying trace points are compatible. One point worth
+ noting is that at this writing, SystemTap scripts must reference probe
+ names using double underlines in place of hyphens. This is expected to
+ be fixed in future SystemTap releases.
+ </para>
+ </note>
+
<para>
You should remember that DTrace scripts need to be carefully written and
debugged, otherwise the trace information collected might
discussing information found using dynamic tracing, be sure to enclose
the script used to allow that too to be checked and discussed.
</para>
+
<para>
More example scripts can be found in the PgFoundry
<ulink url="http://pgfoundry.org/projects/dtrace/">dtrace project</ulink>.