I now did some more tests e.g. driver update new connectionpool but still the
same problem. So I decidet to print and switch to single inserts if batch
was failed.
It seems to be that I did not have a problem, when I switch to
single-insterts so it is not a problem of the data.
Now I believe it is a problem for the combination of colum/batchsize.
Did anyone know a limitation e.g. on JDBC size of limitations?
--
View this message in context: http://postgresql.1045698.n5.nabble.com/LOG-incomplete-message-from-client-tp5801355p5801582.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.