I further analysed this issue and noticed that it is related to PostgreSQL version 9.1. With the version part of the kit, 8.3 there is no issue.
I further analysed this issue and noticed that it is related to PostgreSQL version 9.1. With the version part of the kit, 8.3 there is no issue.