| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pallav Kalva <pkalva(at)livedatagroup(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Invalid String enlargement |
| Date: | 2007-08-18 05:42:15 |
| Message-ID: | 29823.1187415735@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Pallav Kalva <pkalva(at)livedatagroup(dot)com> writes:
> We are planning on upgrading to postgres 8.2.4 from 8.0, we are
> seeing some errors like "invalid string enlargement request size
> 1476395004" after upgrade.
This seems like it must be a server bug, and yet this log trace:
> LOG: incomplete message from client
> ERROR: invalid string enlargement request size 1476395004
> LOG: unexpected EOF on client connection
> LOG: incomplete message from client
> ERROR: invalid string enlargement request size 1476395004
> LOG: unexpected EOF on client connection
suggests that the client side is sending bogus data.
Can you provide a self-contained test case for this?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-18 05:57:57 | Re: compilation error on CentOS 5 |
| Previous Message | Medi Montaseri | 2007-08-17 22:21:02 | compilation error on CentOS 5 |