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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
Cc: korryd(at)enterprisedb(dot)com, 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:40
Message-ID: 12132.1170309580@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> writes:
> 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.

Yeah, that was my problem with the patch too. The issue that it's
addressing isn't Linux-specific in the least.

Is there a way to detect via #if that profiling is enabled? I wouldn't
expect a really portable answer, but maybe there's something that works
for gcc?

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-02-01 06:05:51 Re: DROP FUNCTION failure: cache lookup failed for relation X
Previous Message Mark Kirkwood 2007-02-01 05:59:24 Re: [pgsql-patches] Patch to avoid gprof profilingoverwrites