Re: Proposed changes to DTrace probe implementation

From: Robert Lor <Robert(dot)Lor(at)Sun(dot)COM>
To: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposed changes to DTrace probe implementation
Date: 2008-02-26 15:42:29
Message-ID: 47C43365.5060203@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Lor wrote:
> Proposed changes:
> * Switch from using DTRACE_PROBEn macros to the dynamically generated
> macros (remove pg_trace.h)
> * Use "dtrace -h" to create a header file that contains the
> dynamically generated macros to be used in the source code instead of
> the DTRACE_PROBEn macros.
> * Create a new header file called probes_null.h to map the generated
> macros to no-ops
> * This is unrelated to making DTrace work on Leopard, but I'd like to
> propose that we split the probes into generic database and Postgres
> specific providers, called "database" and "postgresql" respectively.
> Other databases will be adding DTrace probes as well, and we want to
> use "database" as the provider for probes that are common to all
> databases. This way scripts that use the common provider will work on
> databases that implement the common probes.
>
Since I haven't heard any objections, I assume the proposed changes are
acceptable. I'll go a head and submit the patch.

Regards,
-Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2008-02-26 15:43:23 Re: 8.3 / 8.2.6 restore comparison
Previous Message Simon Riggs 2008-02-26 15:36:16 Re: Bulk loading performance improvements