From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | pgsql-general(at)postgresql(dot)org, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Prepared statement performance... |
Date: | 2002-09-25 15:33:28 |
Message-ID: | 3D9224A0.24866.F92EFA3@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
On 25 Sep 2002 at 11:14, Dmitry Tkach wrote:
> Hi, everybody.
>
> I am running into huge performance problems, due to JDBC not being able to cache query plans :-(
> My java program runs the (set of about 5) identical statements with different parameters for about 30 million times...
> What I am talking about below has to do with JDBC, but is not really specific to it - it seems to me, that the backend itself
> could be improved to better handle this kind of scenario, when the same statement is executed many times in the same session.
> - a general solution, that would involve extending postgres SQL gramma to include a 'prepare' statement
Added in upcoming 7.3.. So youmight want to test the betas or CVS..
Just wondering.. Would you see any performance difference in case you put the
statements in pl/pgsql functions?
Just a thought..
Bye
Shridhar
--
The Sixth Commandment of Frisbee: The greatest single aid to distance is for
the disc to be going in a direction you did not want. (Goes the wrong way =
Goes a long way.) -- Dan Roddick
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Welche | 2002-09-25 15:45:29 | FAQ: upgrade recommendation |
Previous Message | Stephan Szabo | 2002-09-25 15:28:21 | Re: Administrator issue |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2002-09-25 17:17:56 | Re: Prepared statement performance... |
Previous Message | Dmitry Tkach | 2002-09-25 15:14:36 | Prepared statement performance... |