Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA31622 for ; Fri, 26 May 2000 12:21:13 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id MAA02364; Fri, 26 May 2000 12:19:52 -0400 (EDT) To: Markus Wagner cc: pgsql-sql Subject: Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state' In-reply-to: <392E17D1.83B13A21@mail.uni-mainz.de> References: <392E17D1.83B13A21@mail.uni-mainz.de> Comments: In-reply-to Markus Wagner message dated "Fri, 26 May 2000 08:21:05 +0200" Date: Fri, 26 May 2000 12:19:52 -0400 Message-ID: <2361.959357992@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/163 Markus Wagner writes: > I am using PG 6.5.1 and DBI. My Perl programs always print to stderr: > "NOTICE: UserAbortTransactionBlock and not in in-progress state" or > "NOTICE: EndTransactionBlock and not inprogress/abort state" > I tried to do -> finish and -> commit after each > query, but the messages still appear. I think you're doing too much rather than too little. Those notices suggest that you're sending out an extra ABORT or COMMIT command after the transaction's already been aborted/committed. IIRC, DBI has an autocommit feature that sends out COMMITs for you. If you have that turned on, *and* you are explicitly committing, then that's probably the cause of the extra commits. Get rid of one or the other. regards, tom lane