Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id AE329632D2C for ; Thu, 28 May 2009 20:20:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 42738-10 for ; Thu, 28 May 2009 20:20:44 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mail.postgresql.org (Postfix) with ESMTP id 62AB0632C13 for ; Thu, 28 May 2009 20:20:50 -0300 (ADT) Received: by rv-out-0506.google.com with SMTP id k40so2273279rvb.43 for ; Thu, 28 May 2009 16:20:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=LEqahM5y810UZzP0fERj/zppT5ASiLdEF2mfmWbhekY=; b=DCcOhP7NVyytlmeiRv+81N2LBPB3g5Oc7TU7jPEexN7uZyiWxSgzQObCTj1SPRx7iJ rOLGKHpgayz1VJpNQd6Z+sKKGgXGJokWUq1qp3ZJ+iDcyq13nyjDcaS2d+DbsGuT++ZN 5/VZtP3VBWkhaB6uMjcyCUzyd601uF1wRocTs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=WLmEWX8nNu4k93a4Xq9/QaevpUnUUAkrDRH40OVlQA+R7OGpvkBHhPHxdGBVfwzAmi LiWpvKtnaWG++ATepdodv62Nqzam3TfwqsVN2CHo7a9olSseP+kdkEIyJXAGkLzIIeOa WuZdQl00w217dpsJUVUCGs4OzS1n4k65/suNw= Received: by 10.143.16.9 with SMTP id t9mr563921wfi.276.1243552848946; Thu, 28 May 2009 16:20:48 -0700 (PDT) Received: from eddie ([67.182.227.82]) by mx.google.com with ESMTPS id 28sm1641012wfg.25.2009.05.28.16.20.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 28 May 2009 16:20:47 -0700 (PDT) Date: Thu, 28 May 2009 17:20:39 -0600 From: Joshua Tolley To: Tom Lane Cc: pgsql-hackers@postgresql.org Subject: Re: Dtrace probes documentation Message-ID: <20090528232039.GD15201@eddie> References: <20090528220739.GA15201@eddie> <1856.1243549694@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zaRBsRFn0XYhEU69" Content-Disposition: inline In-Reply-To: <1856.1243549694@sss.pgh.pa.us> User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL=0.000 X-Spam-Level: X-Archive-Number: 200905/1342 X-Sequence-Number: 138884 --zaRBsRFn0XYhEU69 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 28, 2009 at 06:28:14PM -0400, Tom Lane wrote: > Joshua Tolley 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 discrepanc= y? >=20 > 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, anyth= ing. 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 --zaRBsRFn0XYhEU69 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkofHEcACgkQRiRfCGf1UMN4TgCfXmt6SEs4TISUAxXbHTNMDsm0 JhUAn1mtOwLs+ymVLd5uW4GN5/vVk8E7 =q5tX -----END PGP SIGNATURE----- --zaRBsRFn0XYhEU69--