<br><font size=2 face="sans-serif">On 09/27/2002 10:43:47 PM Barry Lind wrote:<br>
> I think the real question here is when does it make sense to use server<br>
> side prepared statements. In the little bit of testing I have done, I<br>
> would say the answer is rarely. You need many factors to come into<br>
> place for it to make sense to use server side prepared statements:<br>
> <br>
> 1) The statement needs to be big and complex such that there is<br>
> significant overhead in the parsing and planning stages of execution.<br>
</font>
<br><font size=2 face="sans-serif">Hmm, don't know how this relates to PostgreSQL, but I've got an example to the contrary with Oracle (8.1.6).</font>
<br>
<br><font size=2 face="sans-serif">A collegue of mine is developing an application-specific dataloader which does a lot of simple select/update/insert statements. When he changed the (java/JDBC) code from using Statement to PreparedStatement, he got an instant 60% increase in performance.</font>
<br>
<br><font size=2 face="sans-serif">Maarten</font>
<CODE><FONT SIZE=3><BR>
<BR>
------------------------------------------------------------- ---<BR>
Visit our Internet site at http://www.reuters.com<BR>
<BR>
Any views expressed in this message are those of the individual<BR>
sender, except where the sender specifically states them to be<BR>
the views of Reuters Ltd.<BR>
</FONT></CODE>