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

Re: pooled prepared statements

From: Thomas Finneid <tfinneid(at)fcon(dot)no>
To: Dave Cramer <pg(at)fastcrypt(dot)com>
Cc: John Lister <john(dot)lister(at)kickstone(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: pooled prepared statements
Date: 2009-05-13 19:52:03
Message-ID: 4A0B24E3.3070301@fcon.no (view raw or flat)
Thread:
Lists: pgsql-jdbc
Maybe your right. The query processing takes from 1-10 seconds, so 
planning it is not a big factor. But when the load becomes higher, as it 
will be as the data increases, the planning might possibly eat time 
which could be used elsewhere.

My server, as it is now, is pushing the limits of postgres for my use, 
so maybe I need to reclaim as much of wasted time as possible...

We'll see.

thomas

Dave Cramer wrote:
> 
> 
> On Wed, May 13, 2009 at 10:37 AM, John Lister <john(dot)lister(at)kickstone(dot)com 
> <mailto:john(dot)lister(at)kickstone(dot)com>> wrote:
> 
>                 Probably easier to create a server side function
>                 instead, then.
> 
>             But wouldn't you still have to go through all the planning
>             steps within the function for any queries, although i'll
>             admit i'm not familiar with Postgresql functions.
> 
> 
>         Server-side functions are compiled when installed. Since my
>         function would only contain simple queries that are
>         parameterized, it would pre-compile well.
> 
> 
> While the function may be compiled, the overhead is the same for 
> preparing the statement inside the function. So I don't think it's a 
> huge win.
> 


In response to

Responses

pgsql-jdbc by date

Next:From: Dave CramerDate: 2009-05-13 22:31:03
Subject: Re: pooled prepared statements
Previous:From: Dave CramerDate: 2009-05-13 15:21:42
Subject: Re: pooled prepared statements

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