On 18 February 2016 at 05:43, Sridhar N Bamandlapally <sridhar.bn1@gmail.com> wrote:
The code/framework is written to handle batch inserts, which is common for all databases
I feel, PostgreSQL JDBC may need to modify setAutoCommit(false) code to "implicit savepoint - on error - rollback to savepoint"
This would completely nullify the performance advantage of batch inserts. Imagine that instead of sending N inserts we now had to do a savepoint between each one.
PostgreSQL semantics around transaction processing are such that if one fails they all fail. Unless this can be changed in the backend the driver is unlikely to support this.
