Re: New SET/autocommit problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New SET/autocommit problem
Date: 2002-10-22 13:24:30
Message-ID: 17577.1035293070@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sean Chittenden <sean(at)chittenden(dot)org> writes:
> WARNING: COMMIT: no transaction in progress

> I've got tons of these warnings in my logs... is there a programmatic
> way of determining if the current session is in a transaction?

Not at present: you have to track it for yourself. One of the
suggestions on the list for the next frontend/backend protocol revision
(probably in 7.4) is to add a way for the backend to signal its
transaction state: no transaction, in transaction, or in failed
transaction seems like the set of possible states.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-10-22 13:29:22 Re: pg_dump and large files - is this a problem?
Previous Message Philip Warner 2002-10-22 11:46:25 Re: pg_dump and large files - is this a problem?