Database integration is broken for Postgres flavors

Between bitmag 1.2 and 1.3 releases the postgres sql driver was updated from 8.4.x to 9.2.x.
The updated driver have changed behaviour regarding commits on database connections with auto commit enabled (which is default).
In the 8.4.x series calling commit on a connection with auto commit enabled, did not throw an exception. That behaviour is shared with the derby database driver.
In the 9.2.x series, calling commit on a connection with auto commit enabled, throws an SQLException.
A single method in DatabaseUtils (in the bitrepository service module) does this, which renders at least the AuditTrail service, Integrity service and reference/checksum pillar unusable.

There is a workaround, which is to manually replace the postgresql-9.2-1002.jdbc4.jar with the older postgresql-8.4-702.jdbc4.jar found in the 1.2 release.