Re: New SET/autocommit problem

> > 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.

That would be fabulous because with autocommit set to off, the
complexity for tracking that in application is getting pretty
gnarly. -sc

-- 
Sean Chittenden