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

Re: Performance analysis of plpgsql code

From: Michael Fuhr <mike(at)fuhr(dot)org>
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 02:49:18
Message-ID: 20050628024918.GA17735@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-patchespgsql-performance
On Tue, Jun 28, 2005 at 03:03:06AM +0000, Karl O. Pinc wrote:
> 
> For all your work a documentation patch is appended that
> I think is easier to read and might avoid this problem
> in the future.

Patches should go to the pgsql-patches list -- the people who review
and apply patches might not be following this thread.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

pgsql-performance by date

Next:From: Karl O. PincDate: 2005-06-28 03:03:06
Subject: Re: Performance analysis of plpgsql code
Previous:From: David MitchellDate: 2005-06-28 02:37:34
Subject: How can I speed up this function?

pgsql-patches by date

Next:From: Jim C. NasbyDate: 2005-06-28 02:58:22
Subject: Re: Problem with dblink regression test
Previous:From: Tom LaneDate: 2005-06-28 02:39:55
Subject: Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

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