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 44C225F8.5010206@sun.com
Whole thread Raw
Responses Re: [PATCHES] Generic Monitoring Framework with DTrace patch  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut wrote:

>Here is a consolidated patch that contains all the files.  I made some 
>configure and makefile adjustments and put standard comment headers in 
>all the files.  You can use DTRACEFLAGS to pass options to configure, 
>which should help sorting out the 32/64-bit issue.  The problem of the 
>*.d files is already gone in CVS.
>
>Since I don't have access to a Solaris system, this is untested for the 
>DTrace-enabled case.  The only thing left to do besides actually 
>testing that case would be moving the probes.d file to a different 
>location, since we probably don't want to have special-purpose files in 
>src/backend.
>
>  
>
I can't seem to apply the patch on Solaris. I ran the patch command from 
the top of the src tree and got the following messages. When I tried to 
enter a file name, it goes into infinite loop. What did I do wrong?

-bash-3.00$ patch -p0 -u < /var/tmp/dtrace-patch.diff Looks like a unified context diff. The next patch looks like a
unifiedcontext diff. The next patch looks like a unified context diff. The next patch looks like a unified context
diff.The next patch looks like a unified context diff.
 
File to patch:


Regards,
-Robert



pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: "hot standby" system
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCHES] Generic Monitoring Framework with DTrace patch