Re: Patch to avoid gprof profiling overwrites

From: <korryd(at)enterprisedb(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Patch to avoid gprof profiling overwrites
Date: 2007-01-31 22:59:21
Message-ID: 1170284361.6941.115.camel@sakai.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> And the patch is where?

You caught me; guess I'd better make something up fast, huh?

Here it is, thanks.

-- Korry

>
> ---------------------------------------------------------------------------
>
> korryd(at)enterprisedb(dot)com wrote:
> > It's difficult to profile a backend server process (using gprof)
> > because each process overwrites any earlier profile as it exits.
> >
> > It is especially tricky to nab a useful profile if you happen to have
> > autovacuum enabled.
> >
> > This patch reduces the problem by forcing the backend to 'cd' to a new
> > directory ($PGDATA/gprof/pid) just before calling exit(), but only if
> > the backend was compiled with -DLINUX_PROFILE.
> >
> > I've tested this with Linux, but not with other host architectures.
> >
> > -- Korry
> >
> >
> >
> > --
> > Korry Douglas korryd(at)enterprisedb(dot)com
> > EnterpriseDB http://www.enterprisedb.com
>

--
Korry Douglas korryd(at)enterprisedb(dot)com
EnterpriseDB http://www.enterprisedb.com

Attachment Content-Type Size
gprof.patch text/x-patch 1.7 KB

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Mark Kirkwood 2007-02-01 01:17:24 Re: [pgsql-patches] Patch to avoid gprof profiling overwrites
Previous Message Neil Conway 2007-01-31 17:51:44 Re: uuid patch 3.0 (8.3devel)