To: William Lawrance
> Cc: Michael Meskes; Pgsql-Patches
> Subject: Re: [PATCHES] ECPG patch to use prepare for improved
> performance
>
>
> On Wed, May 09, 2007 at 01:12:17PM -0700, William Lawrance wrote:
> > 2. The performance was improved by about 1 hour in the
es
Subject: Re: [PATCHES] ECPG patch to use prepare for improved
performance
On Wed, May 09, 2007 at 01:12:17PM -0700, William Lawrance wrote:
2. The performance was improved by about 1 hour in the 3 hour
elapsed time of the application. This is important to the
customer in terms of acc
ay, May 10, 2007 3:01 AM
To: William Lawrance
Cc: Michael Meskes; Pgsql-Patches
Subject: Re: [PATCHES] ECPG patch to use prepare for improved
performance
On Wed, May 09, 2007 at 01:12:17PM -0700, William Lawrance wrote:
> 2. The performance was improved by about 1 hour in the 3 hour
>ela
On Wed, May 09, 2007 at 01:12:17PM -0700, William Lawrance wrote:
> 2. The performance was improved by about 1 hour in the 3 hour
>elapsed time of the application. This is important to the
>customer in terms of accomplishing his work load in the
>time that has been allotted, based on
William Lawrance wrote:
> This approach was used for several reasons--
>
> 1. No changes were required in the application source program. For
>an application involving thousands of SQL statements in hundreds
>of programs, this is important. This customer application has
>been tuned ext
ubject: Re: [PATCHES] ECPG patch to use prepare for improved
performance
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. I
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 unders
