pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'
3+ messages / 3 participants
[nested] [flat]

* PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'
@ 2000-05-26 06:21  Markus Wagner <mawagner@mail.uni-mainz.de>
  0 siblings, 2 replies; 3+ messages in thread

From: Markus Wagner @ 2000-05-26 06:21 UTC (permalink / raw)
  To: pgsql-sql

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?

Thanks,

Markus




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'
@ 2000-05-26 13:42  Ed Loehr <eloehr@austin.rr.com>
  parent: Markus Wagner <mawagner@mail.uni-mainz.de>
  1 sibling, 0 replies; 3+ messages in thread

From: Ed Loehr @ 2000-05-26 13:42 UTC (permalink / raw)
  To: Markus Wagner <mawagner@mail.uni-mainz.de>; +Cc: 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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state'
@ 2000-05-26 16:19  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Markus Wagner <mawagner@mail.uni-mainz.de>
  1 sibling, 0 replies; 3+ messages in thread

From: Tom Lane @ 2000-05-26 16:19 UTC (permalink / raw)
  To: Markus Wagner <mawagner@mail.uni-mainz.de>; +Cc: 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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2000-05-26 16:19 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-05-26 06:21 PG/DBI: 'NOTICE: UserAbortTransactionBlock and not in in-progress state' Markus Wagner <mawagner@mail.uni-mainz.de>
2000-05-26 13:42 ` Ed Loehr <eloehr@austin.rr.com>
2000-05-26 16:19 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox