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

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

From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
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 13:42:36
Message-ID: 392E7F4C.AA455FAA@austin.rr.com (view raw or flat)
Thread:
Lists: pgsql-sql
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 <stmthandle> -> finish and <dbhandle> -> 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

In response to

pgsql-sql by date

Next:From: Mitch VincentDate: 2000-05-26 14:31:04
Subject: date() indexing error..
Previous:From: Peter EisentrautDate: 2000-05-26 13:02:53
Subject: Re: aliases break my query

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