| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:33:05 |
| Message-ID: | 20080704173305.GD3893@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> Tom Lane napsal(a):
>> I see no value in cluttering the system with useless probes. The worker
>> start/stop are the only ones here with any conceivable application IMHO.
>
> As I answered to Alvaro. I needed to catch start of backend several times
> to track call flow or attach debugger. It is possible to use some other
> dtrace magic for that, but it is not easy and there is not way how to
> determine what kind of process it is. For example how to measure how
> many writes performs bgwriter?
If you need to attach a debugger to a backend, you can use the -W switch
(even on PGOPTIONS if you need it for a particular backend, AFAIR). If
you want to "truss" it I guess you can use -W too.
Does it have any usefulness beyond that?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-07-04 17:42:12 | Re: Review: DTrace probes (merged version) |
| Previous Message | Alvaro Herrera | 2008-07-04 17:30:35 | Re: Review: DTrace probes (merged version) |