From: | "Brett" <brettonator(at)excite(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Taking advantage of prepared statement performance |
Date: | 2002-10-10 17:34:03 |
Message-ID: | 20021010173403.510C429A1B@xmxpita.excite.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Correction... version is 7.3b2--- On Thu 10/10, Brett < brettonator(at)excite(dot)com > wrote:
From: Brett [mailto: brettonator(at)excite(dot)com]To: pgsql-jdbc(at)postgresql(dot)orgDate: Thu, 10 Oct 2002 13:30:00 -0400 (EDT)Subject: [JDBC] Taking advantage of prepared statement performance
I have a web application that invokes java jdbc code for each request. Wouldit be faster if I stored all my prepared statements for each connection, sowhen I want to do a query I a) pull a connection object from the pool thenb) call ps.setX; ps.setY;...; ps.executeQuery(); and not close the preparedstatement? That way, another thread could grab the connection and nothave to recreate the prepared statement. I would associate sets ofprepared statements with connections. Would this be faster thancreating a prepared statement for each web request?I am using 7.1.3b2 (for production *crosses fingers*) in case that matters.Once again thanks for any help and sorry for any formatting issues withthis message.
------------------------------------------------
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-10-10 17:48:02 | Re: Taking advantage of prepared statement performance |
Previous Message | Brett | 2002-10-10 17:30:00 | Taking advantage of prepared statement performance |