Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.3/8.9.3) with ESMTP id QAA56136
	for <pgsql-interfaces@postgreSQL.org>;
	Thu, 27 May 1999 16:45:18 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id QAA23469;
	Thu, 27 May 1999 16:44:47 -0400 (EDT)
To: Peter T Mount <peter@retep.org.uk>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Re: [GENERAL] JDBC and insert - stack overflow 
In-reply-to: Your message of Thu, 27 May 1999 18:24:50 +0100 (GMT)
	<Pine.LNX.4.04.9905271822440.2157-100000@maidast.retep.org.uk>
Date: Thu, 27 May 1999 16:44:47 -0400
Message-ID: <23467.927837887@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Peter T Mount <peter@retep.org.uk> writes:
>> By the way, use con.setAutoCommit( false ) to have all the inserts in one
>> big transaction. It saves a lot of time.

> Don't forget to commit() at the end, as you can't guarantee that a
> transaction will be committed when the connection closes.

In fact, I believe that we guarantee the opposite: any open transaction
will be aborted if the client closes the connection without sending a
commit command...

			regards, tom lane