Skip site navigation (1) Skip section navigation (2)

Re: Performance analysis of plpgsql code

From: Michael Glaesemann <grzm(at)myrealbox(dot)com>
To: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance analysis of plpgsql code
Date: 2005-06-28 01:15:50
Message-ID: 00AC59C9-7A32-40A6-80A7-B5428F02D0E6@myrealbox.com (view raw or flat)
Thread:
Lists: pgsql-patchespgsql-performance
On Jun 28, 2005, at 10:54 AM, Karl O. Pinc wrote:

>
> 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.

I recommend you look again.

<http://www.postgresql.org/docs/8.0/interactive/functions- 
datetime.html#FUNCTIONS-DATETIME-CURRENT>

Michael Glaesemann
grzm myrealbox com

In response to

pgsql-performance by date

Next:From: Leigh DyerDate: 2005-06-28 01:24:48
Subject: Faster drives for WAL than for data?
Previous:From: Michael FuhrDate: 2005-06-27 23:33:03
Subject: Re: Performance analysis of plpgsql code

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2005-06-28 01:29:40
Subject: Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector
Previous:From: Bruce MomjianDate: 2005-06-28 01:13:20
Subject: Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group