Re: [PATCHES] Generic Monitoring Framework with DTrace patch - Mailing list pgsql-hackers

From Robert Lor
Subject Re: [PATCHES] Generic Monitoring Framework with DTrace patch
Date
Msg-id 44C0ECD3.6090004@sun.com
Whole thread Raw
In response to Re: [PATCHES] Generic Monitoring Framework with DTrace patch  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCHES] Generic Monitoring Framework with DTrace patch  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut wrote:

>I would prefer to drop the PG_ prefixes on PG_TRACE and pg_trace.h.  We 
>know which software we're dealing with.
>
>  
>
I also agree with Martin & Tom to keep the PG_ prefixes.

>We should probably move the probes file to a subdirectory.  Anyone know 
>a good place?
>
>Also, again, the pgsql prefix should be dropped.
>  
>
To keep it consistent with the header file, perhaps it can be renamed to 
pg_probes.d

>Certainly doable, but will that be more reliable?  Can't we convince 
>dtrace to create binaries for the host platform by default?
>  
>
The user needs to have the flexibility to build a 32 bit PG binary even 
when he run the 64 bit kernel. If I understand you correctly, your 
suggestion will not allow a 32 bit binary to be built on a 64 bit OS.

>>3)  When using --enable-depend, "gmake clean" removes all *.d files,
>>    
>>
>
>I'm working on renaming the dependency files.
>
>  
>
Excellent!

Thanks Peter for your help!

Regards,
-Robert



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Generic Monitoring Framework with DTrace
Next
From: Robert Lor
Date:
Subject: Re: [PERFORM] Sun Donated a Sun Fire T2000 to the PostgreSQL