Rollback is called on Postgres DB when closing connection

Rollback is called on Postgres DB when closing connection

Postby marek.kulvejt » Thu 30 Jul 2009 12:10


we get 'NOTICE: there is no transaction in progress' message on the server when closing a connection that contained a transaction. Pseudo code:

using (PgSqlConnection conn = new PgSqlConnection(..))

using (PgSqlTransaction trans = conn.BeginTransaction(...))
...execute command under the transaction

if (everythingWentOk)
} // !!!! There is the problem here: when executing "conn.Close()", the DB server complains

When we call conn.Commit() the situation does not change.

What are we doing wrong? Is it a bug in the dotConnect driver?

Thanks in advance,
Marek Kulvejt

P.S. The data are stored well and everything seems to work. The problem is that we save a lot of data and we get approx. 1GB of log every day. Moreover, the database itself must do some work just to execute an useless command.
Posts: 5
Joined: Mon 06 Jul 2009 08:50

Postby Shalex » Fri 31 Jul 2009 12:58

This is a designed behaviour. It is necessary to make rollback for the connection before placing it back to pool. As a workaround, you can turn off connection pooling (the Pooling=false; entry in the connection string).
Devart Team
Posts: 7654
Joined: Thu 14 Aug 2008 12:44

Return to dotConnect for PostgreSQL