Re: LOG: incomplete message from client - Mailing list pgsql-bugs

From Tomas Vondra
Subject Re: LOG: incomplete message from client
Date
Msg-id 535C1E92.2020000@fuzzy.cz
Whole thread Raw
In response to Re: LOG: incomplete message from client  (tcoq <steffen.otto@dologo.de>)
List pgsql-bugs
On 26.4.2014 06:47, tcoq wrote:
> 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?

So, what connection pool(s) are you using?

Can you prepare a self-contained test case?

regards
Tomas

pgsql-bugs by date:

Previous
From: sdfasdf asdfasdf
Date:
Subject: Re[2]: [BUGS] Re[2]: [BUGS] BUG #10140: Configured for 127.0.0.1 but binds to all IP
Next
From: 德哥
Date:
Subject: Re: BUG #10144: PostgreSQL cost_index in costsize.c bug? (cann't estimate indexCorrelation correct)