From: Joshua Tolley <eggyknap@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Dtrace probes documentation
Date: Thu, 28 May 2009 17:20:39 -0600
Message-ID: <20090528232039.GD15201@eddie> (raw)
In-Reply-To: <1856.1243549694@sss.pgh.pa.us>
References: <20090528220739.GA15201@eddie>
<1856.1243549694@sss.pgh.pa.us>
On Thu, May 28, 2009 at 06:28:14PM -0400, Tom Lane wrote:
> Joshua Tolley <eggyknap@gmail.com> writes:
> > 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?
>
> Read 26.4.3 and .4. I don't know why they have this bizarre set of
> conventions, but the single-hyphen version is the spelling
> most visible to end users.
I thought it might be something like that. I've been playing with SystemTap,
and found that only the double-underscore version works for ... well, anything.
See http://blog.endpoint.com/2009/05/postgresql-with-systemtap.html for
details. Perhaps it's worth noting in the documentation that SystemTap users
will need to use the double-underscore version?
- Josh / eggyknap
Attachments:
[application/pgp-signature] signature.asc (196B, ../20090528232039.GD15201@eddie/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: eggyknap@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Dtrace probes documentation
In-Reply-To: <20090528232039.GD15201@eddie>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox