> > WARNING: COMMIT: no transaction in progress > > COMMIT > > > The WARNING happens with SHOW and RESET too. I wonder if we should > > suppress the WARNING of a COMMIT with no statements when autocommit is > > off. > > I don't think so; that will make it quite hard to check whether a > transaction is open.
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? Unless I misunderstood the fix and the commit message, I'm pretty sure that most of my problem has been fixed in CVS with SET's auto-committing if it's not in a transaction, but now that there are some intricate rules with regards to starting transactions, I'd love to provide a DBI interface into a call that returns whether or not we're in a transaction to prevent millions of these: NOTICE: ROLLBACK: no transaction in progress -sc -- Sean Chittenden ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
