From: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance analysis of plpgsql code |
Date: | 2005-06-28 01:54:08 |
Message-ID: | 1119923648l.11411l.0l@mofo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches pgsql-performance |
On 06/27/2005 06:33:03 PM, Michael Fuhr wrote:
> On Mon, Jun 27, 2005 at 11:30:45PM +0000, Karl O. Pinc wrote:
> >
> > Short of that I think I'm going to be reduced to
> > writing a C function that returns the real
> > system time so I can spatter my code with
> > RAISE statements that indicate actual execution
> > time.
>
> See timeofday().
That only gives you the time at the start of the transaction,
so you get no indication of how long anything in the
transaction takes.
Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-28 02:39:55 | Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector |
Previous Message | Michael Fuhr | 2005-06-28 01:34:19 | Re: Performance analysis of plpgsql code |
From | Date | Subject | |
---|---|---|---|
Next Message | Karl O. Pinc | 2005-06-28 02:36:51 | Re: Poor index choice -- multiple indexes of the same |
Previous Message | Michael Fuhr | 2005-06-28 01:34:19 | Re: Performance analysis of plpgsql code |