Re: [pgsql-patches] Patch to avoid gprof profilingoverwrites

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: korryd(at)enterprisedb(dot)com
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: [pgsql-patches] Patch to avoid gprof profilingoverwrites
Date: 2007-02-01 05:59:24
Message-ID: 45C181BC.8000307@paradise.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Mark Kirkwood wrote:
> korryd(at)enterprisedb(dot)com wrote:
>>> The name for the define variable could perhaps be better - feels
>>> silly adding -DLINUX_PROFILE on Freebsd! (maybe just PROFILE or
>>> GPROF_PROFILE?).
>>
>> That wasn't my choice, there is other code elsewhere that depends on
>> that symbol, I just added a little bit more.
>>
>
> Right - but LINUX_PROFILE was added to correct Linux specific oddities
> with the time counter accumulation, whereas your patch is not Linux
> specific at all. So I think a more representative symbol is required.
>

In fact - thinking about this a bit more, probably a construction like:

#if defined(LINUX_PROFILE) || defined(PROFILE)

or similar would work - because I think those of us not on Linux do
*not* want to define LINUX_PROFILE, as our timer accumulation for forked
process works fine as it is...but we don't want to make Linux guys have
to define LINUX_PROFILE *and* PROFILE...

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-01 05:59:40 Re: [pgsql-patches] Patch to avoid gprof profilingoverwrites
Previous Message Mark Kirkwood 2007-02-01 05:52:57 Re: [pgsql-patches] Patch to avoid gprof profilingoverwrites