From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | William Lawrance <bill(dot)lawrance(at)bull(dot)com> |
Cc: | Pgsql-Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: ECPG patch to use prepare for improved performance |
Date: | 2007-05-09 09:04:03 |
Message-ID: | 20070509090403.GB18105@feivel.credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Mon, May 07, 2007 at 02:46:29PM -0700, William Lawrance wrote:
> This patch for ECPG utilizes the "PQprepare" and "PQexecPrepared"
> functions to cause SQL statements from ECPG to be cached. It does
> this without requiring any changes in the user's source program.
> ...
I still do not understand why you prepare each statement. This might
help you with your test case, but I don't like to add this as a general
rule. If a user wants a prepared statement he/she should use the prepare
statement. I agree that the prepare logic has to be rewritten and this
is high on my agenda, but I will probably only do this for statements
issued with EXEC SQL PREPARE not for every single statement.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-05-09 17:28:58 | Doc and comment patch for packed varlena |
Previous Message | Peter Eisentraut | 2007-05-09 08:10:50 | Re: [WIP] GUC for temp_tablespaces |