Re: Invalid String enlargement - Mailing list pgsql-admin

From Tom Lane
Subject Re: Invalid String enlargement
Date
Msg-id 29823.1187415735@sss.pgh.pa.us
Whole thread Raw
In response to Invalid String enlargement  (Pallav Kalva <pkalva@livedatagroup.com>)
Responses Re: Invalid String enlargement  (Pallav Kalva <pkalva@livedatagroup.com>)
List pgsql-admin
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:

>    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

pgsql-admin by date:

Previous
From: "Medi Montaseri"
Date:
Subject: compilation error on CentOS 5
Next
From: Tom Lane
Date:
Subject: Re: compilation error on CentOS 5