On Sun, 20 Apr 2008, David Wall wrote:
Just checking if the JDBC library's batch processing code is more efficient
with respect to the postgresql back end or not. Does it really batch the
requests and submit them once over the link, or does it just send them to the
database to be processed
Does this means that the two features are independent one from each other ?
In other words, can we say that JDBC batch will limit information
exchange between client and server while Postgres prepared statements
will optimize their execution ?
Kris Jurka ha scritto:
On Sun, 20 Apr 2008,
The JDBC driver's batch processing is more efficient than regular
execution because it requires fewer network roundtrips so there's less
waiting. The JDBC batch is broken into an internal batch size of 256
statement and all of these are sent over to the server at once.
That's great, Kris.
Does this means that the two features are independent one from each
other ?
In other words, can we say that JDBC batch will limit information
exchange between client and server while Postgres prepared statements
will optimize their execution ?
I've not used it yet, but my impression is that
Just checking if the JDBC library's batch processing code is more
efficient with respect to the postgresql back end or not. Does it
really batch the requests and submit them once over the link, or does it
just send them to the database to be processed one at a time?
Thanks,
David
--
Sent
