Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state' - Mailing list pgsql-sql

From Tom Lane
Subject Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'
Date
Msg-id 2361.959357992@sss.pgh.pa.us
Whole thread Raw
In response to PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'  (Markus Wagner <mawagner@mail.uni-mainz.de>)
List pgsql-sql
Markus Wagner <mawagner@mail.uni-mainz.de> 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 <stmthandle> -> finish and <dbhandle> -> 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


pgsql-sql by date:

Previous
From: "Wallingford, Ted"
Date:
Subject: RE: POSTGRESQL and PERL?
Next
From: Tom Lane
Date:
Subject: Re: aliases break my query