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 47C45E00.40404@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 unconvinced that there will be any probes that are common to all
> databases.  I'd skip this part...
>
>   
Any reason why we can't consider probes like transaction-start, 
transaction-commit, or transaction-abort as common probes that can also 
be used in other (maybe no all) databases?  We are only talking about 
the probe definition here as shown below, not how they will be implemented.

probe transaction__start(int);
probe transaction__commit(int);
probe transaction__abort(int);


Regards,
-Robert




pgsql-hackers by date:

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