| From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Lor <Robert(dot)Lor(at)Sun(dot)COM>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, jesus(at)omniti(dot)com |
| Subject: | Re: Review: DTrace probes (merged version) |
| Date: | 2008-07-04 17:42:12 |
| Message-ID: | 486E60F4.7080706@sun.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera napsal(a):
> Zdenek Kotala wrote:
>> Alvaro Herrera napsal(a):
>
>>>> proc-master-start
>>>> proc-master-stop
>>> What's "master" here?
>> Main process - postmaster.
>
> Huh, surely we're not interested in tracking postmaster start?
>
It depends. See following schema example
postgres::proc-master-start
{
tracking = 1
}
syscall:::open:entry
/ tracking == 1/
{
... print file name ...
}
postgres::proc-master-stop
{
tracking = 0
}
It is very useful because it say when you can start and stop monitoring for
example. But I'm not DTrace expert maybe there is different way how to do it.
Zdenek
--
Zdenek Kotala Sun Microsystems
Prague, Czech Republic http://sun.com/postgresql
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-07-04 17:50:18 | Re: Review: DTrace probes (merged version) |
| Previous Message | Alvaro Herrera | 2008-07-04 17:33:05 | Re: Review: DTrace probes (merged version) |