Skip site navigation (1) Skip section navigation (2)

Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Markus Wagner <mawagner(at)mail(dot)uni-mainz(dot)de>
Cc: pgsql-sql <pgsql-sql(at)postgresql(dot)org>
Subject: Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'
Date: 2000-05-26 16:19:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
Markus Wagner <mawagner(at)mail(dot)uni-mainz(dot)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

In response to

pgsql-sql by date

Next:From: Tom LaneDate: 2000-05-26 16:26:06
Subject: Re: aliases break my query
Previous:From: Wallingford, TedDate: 2000-05-26 16:14:16

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group