Received: from Mail.austin.rr.com (sm2.texas.rr.com [24.93.35.55]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA26849 for ; Fri, 26 May 2000 09:39:11 -0400 (EDT) (envelope-from eloehr@austin.rr.com) Received: from austin.rr.com ([24.93.36.232]) by Mail.austin.rr.com with Microsoft SMTPSVC(5.5.1877.357.35); Fri, 26 May 2000 08:24:44 -0500 Message-ID: <392E7F4C.AA455FAA@austin.rr.com> Date: Fri, 26 May 2000 08:42:36 -0500 From: Ed Loehr X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12-20smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Markus Wagner CC: pgsql-sql Subject: Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state' References: <392E17D1.83B13A21@mail.uni-mainz.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200005/158 Markus Wagner wrote: > > Hi, > > 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. > > Any hints? I think that happens if the backend aborted (elogged) with an ERROR message and you did not start a new transaction. ERROR kills the current transaction altogether in 6.5.*, IIRC. Regards, Ed Loehr