Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id CC56C9FA2CA for ; Thu, 30 Nov 2006 21:10:48 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 58232-01 for ; Thu, 30 Nov 2006 21:10:39 -0400 (AST) X-Greylist: delayed 00:40:00.804122 by SQLgrey-1.7.4 Received: from mail.omniti.com (mail.omniti.com [66.225.209.50]) by postgresql.org (Postfix) with ESMTP id 62DB49FA282 for ; Thu, 30 Nov 2006 21:10:43 -0400 (AST) Authentication-Results: mail.omniti.com smtp.user=robert; auth=pass (LOGIN) Received: from ([10.80.116.148:60884] helo=[10.80.116.148]) by mail.omniti.com (ecelerity 2.1.1.1-psycho r(11653M)) with ESMTPSA (cipher=EXP1024-RC4-SHA) id 18/63-19070-8A77F654 for ; Thu, 30 Nov 2006 19:30:39 -0500 From: Robert Treat To: pgsql-docs@postgresql.org Subject: Re: DTrace docs, Open Items and Performance Date: Thu, 30 Nov 2006 19:30:31 -0500 User-Agent: KMail/1.9.1 Cc: Tom Lane , Peter Eisentraut , "Simon Riggs" References: <1164710275.3778.464.camel@silverbirch.site> <200611281209.27611.peter_e@gmx.net> <5658.1164726337@sss.pgh.pa.us> In-Reply-To: <5658.1164726337@sss.pgh.pa.us> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200611301930.31669.xzilla@users.sourceforge.net> Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/89 X-Sequence-Number: 3923 On Tuesday 28 November 2006 10:05, Tom Lane wrote: > Peter Eisentraut writes: > > Simon Riggs wrote: > >> I'm planning to > >> - add a new section to Performance Tips chapter called Dynamic > > > > In my mind it's a little late for revising the documentation structure. > > I'd also think that DTrace is not a tuning tool but a monitoring tool > > which might place it closer to the description of the statistics > > collector. I think the original plan even placed it into the Internals > > part. > > I was about to say the same. In my mind DTrace is primarily a hacker's > tool --- I do not foresee the average DBA using it. So it does not > belong in the Performance Tips chapter. A new chapter under Internals > is probably as good as anything. > I'm not certain how best the postgresql specific probes will be used, but I might disagree with the above take as we're already using some kernel level dtrace probes to make DBA oriented tools... see http://www.lethargy.org/~jesus/archives/74-PostgreSQL-performance-through-the-eyes-of-DTrace.html for one specific example. -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL