Re: Proposed changes to DTrace probe implementation - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: Proposed changes to DTrace probe implementation
Date
Msg-id 87zltneady.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Proposed changes to DTrace probe implementation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposed changes to DTrace probe implementation
List pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> Possibly I have a different view of the uses of dtrace than you do, but
> most of the events I'd be interested in probing are probably pretty
> Postgres-specific.  

I think both types of probes are useful to different people.

One of the really neat things about dtrace, imho, is that it lets you
correlate data from different levels of abstraction. You can find out how many
physical i/o's happen per i/o syscall. And how many i/o syscalls per database
transaction. And how many database transactions per application request. Etc.

Perhaps looking at the standard database SNMP MIB counters would give us a
place to start for upward facing events people want to trace for databases in
general.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production
Tuning


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Two Coverity Scan volunteers needed
Next
From: Neil Conway
Date:
Subject: Re: Two Coverity Scan volunteers needed