Re: [PATCH] dtrace probes for memory manager

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] dtrace probes for memory manager
Date: 2009-12-11 20:23:18
Message-ID: 1260562998.2642.71.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane píše v pá 11. 12. 2009 v 15:11 -0500:
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> > I thought about it. I think we can use GUC variable (e.g. dtraced_alloc)
> > and hook switch pointers to dtraced AsetFunctions. The problem is how to
> > distribute to all backend.
>
> You set the GUC in postgresql.conf. No big deal.
>
> If we go this route it would be nice to think about making a facility
> that has some usefulness for non-DTrace platforms too.

Do you mean general facility for switching memory allocator?

Zdenek

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Smalley 2009-12-11 20:25:19 Re: Adding support for SE-Linux security
Previous Message Tom Lane 2009-12-11 20:20:58 Re: thread safety on clients