| From: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: LOG: incomplete message from client |
| Date: | 2014-04-26 21:01:06 |
| Message-ID: | 535C1E92.2020000@fuzzy.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 德哥 | 2014-04-27 02:18:27 | Re: BUG #10144: PostgreSQL cost_index in costsize.c bug? (cann't estimate indexCorrelation correct) |
| Previous Message | sdfasdf asdfasdf | 2014-04-26 20:01:34 | Re[2]: [BUGS] Re[2]: [BUGS] BUG #10140: Configured for 127.0.0.1 but binds to all IP |