| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Subject: | Re: [PATCH] dtrace probes for memory manager |
| Date: | 2009-11-13 21:25:33 |
| Message-ID: | 1258147533.14849.387.camel@jd-desktop.unknown.charter.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2009-11-13 at 15:22 -0600, Kevin Grittner wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
>
> > Is it possible to have a set of probes that would only be enabled
> > with say, --enable-debug compile time option?
>
> But we routinely build with that for normal production use so that if
> we get a core dump or need to backtrace a problem process, we will get
> meaningful results. Please don't create a performance penalty for
> compiling with debug info. (We'd probably wind up disabling it....)
Good point but I still say that the probes are useful. I am not sure we
have a good compile time flag for it right now but it seems that would
be the way to do it.
Joshua D. Drake
>
> -Kevin
>
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
If the world pushes look it in the eye and GRR. Then push back harder. - Salamander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2009-11-13 21:29:28 | Re: Experimental patch: generating BKI revisited |
| Previous Message | Dan Colish | 2009-11-13 21:25:13 | Re: CommitFest 2009-11: Almost done with initial assignments |