Re: deadlocks in postgresql 7.2.1

From: Dmitry Tkach <dmitry(at)openratings(dot)com>
To: Philipp Reisner <philipp(dot)reisner(at)linbit(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: deadlocks in postgresql 7.2.1
Date: 2003-07-28 16:49:45
Message-ID: 3F255429.9000106@openratings.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>
>
>
>Thanks a lot for the reply!
>
>The applications uses the jdbc driver with autocommit turned off,
>commit and rollback. Do you know if the jdbc driver just starts
>a new transaction as soon as the last one was ended with commit/
>rollback ?
>
>
Yes, it does.
You have to explictly setAutocommit(true) instead of commit() (or, you
can commit(), and *then* setAutocommit(true) if you want, the result is
the same).

I hope, it helps....

Dima

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Hunter Hillegas 2003-07-28 17:19:37 Re: Can't Build 7.3.4 on OS X
Previous Message Philipp Reisner 2003-07-28 13:55:05 Re: deadlocks in postgresql 7.2.1