Hi Andrus,
i got an useful hint that this "bug" is based on the jdbc-driver from
postgres.
I also found this info:
http://jdbc.postgresql.org/changes.html#version_dev302
"Track transaction status and only issue a BEGIN command on the first
statement executed, not immediately after the previous commit or
rollback. This should help the long standing, but recently very
unpopular "idle in transaction" behavior. (jurka)"
Greetings
Oilid
This archive was generated by hypermail 2.0.0 : Tue Apr 24 2007 - 07:13:01 EDT