Re: Invalid String enlargement

Tom Lane wrote:
> Pallav Kalva <pkalva@livedatagroup.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:
>
We are on Suse 10.1 , are there any issues that you know of on Suse 10.1
and postgres 8.2.4 ?
>
>>    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?
>
Unfortunately we tried but we cant figure out exactly what causing it ,
everything seems to be OK at the client side, application is also
working fine , we see these errors only in postgres logs.

We are using connecting pooling if that helps in any way.

>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: You can help support the PostgreSQL project by donating at
>
>                 http://www.postgresql.org/about/donate
>