Re: not exactly a bug report, but surprising behaviour

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: not exactly a bug report, but surprising behaviour
Date: 2003-02-05 23:32:46
Message-ID: 87d6m6482p.fsf@stark.dyndns.tv
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Neil Conway <neilc(at)samurai(dot)com> writes:

> On Wed, 2003-02-05 at 15:49, Greg Stark wrote:
> > % cumulative self self total
> > time seconds seconds calls s/call s/call name
> > 16.59 97.88 97.88 69608411 0.00 0.00 ExecMakeFunctionResult
> > 7.08 139.65 41.77 79472258 0.00 0.00 comparetup_heap
> > 4.50 166.17 26.52 192211935 0.00 0.00 ExecEvalExpr
>
> (Semi OT)
>
> Annoyingly enough, I get similarly strange gprof output (all zeros in
> the two right hand columns) on Debian -- PostgreSQL compiled with
> -DLINUX_PROFILE -pg using gcc 3.2.2pre, glibc 2.3.1, binutils
> 2.13.90.0.16. I haven't been able to figure out what the problem is,
> though.
>
> If anyone has any suggestions on how to fix this, please speak up.

Well this is Debian also, but I don't think that's related. Those two columns
are "seconds per call". Look at how many calls those functions have, they take
very little time per call, much less than 1/100th of a second.

--
greg

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vince Vielhaber 2003-02-06 00:13:54 Re: [ANNOUNCE] PostgreSQL v7.3.2 Released
Previous Message Andrew Sullivan 2003-02-05 22:54:49 Re: IN() alternatives