From: Michael Fuhr <mike@fuhr.org>
To: Karl O. Pinc <kop@meme.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance analysis of plpgsql code
Date: Mon, 27 Jun 2005 20:49:18 -0600
Message-ID: <20050628024918.GA17735@winnie.fuhr.org> (raw)
In-Reply-To: <1119927786l.11411l.3l@mofo>
References: <1119915045l.4428l.5l@mofo>
<20050627233303.GA17069@winnie.fuhr.org>
<1119923648l.11411l.0l@mofo>
<20050628013419.GA17407@winnie.fuhr.org>
<1119927786l.11411l.3l@mofo>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mike@fuhr.org, kop@meme.com
Subject: Re: Performance analysis of plpgsql code
In-Reply-To: <20050628024918.GA17735@winnie.fuhr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox