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

From Robert Lor
Subject Re: Proposed changes to DTrace probe implementation
Date
Msg-id 47C46C40.9000907@sun.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 wrote:
> I'm unimpressed; it's not at all clear that you'd be measuring quite the
> same thing in, say, mysql as in postgres.
>   
I think it depends on the probe, but for transaction rates like start or 
commit, don't you think it's pretty black & white as long as the probes 
are placed in the correct locations.
> 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 agree that most probes, especially low level ones, will be Postgres 
specific.
>   I think distinguishing half a dozen of them on the
> assumption that there should be (exact) matches to that probe point in
> most databases is misleading and a source of useless extra notation.
>
>   
This is just forward looking on my part since other OS databases will 
most likely be adding Dtrace probes as well.  I'll put them back 
together in one provider for now!

Regards,
-Robert



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: pg_dump additional options for performance
Next
From: "Joshua D. Drake"
Date:
Subject: Re: pg_dump additional options for performance