pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pallav Kalva <pkalva@livedatagroup.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Invalid String enlargement
Date: Mon, 20 Aug 2007 09:44:24 -0400
Message-ID: <46C99AB8.4000102@livedatagroup.com> (raw)
In-Reply-To: <29823.1187415735@sss.pgh.pa.us>
References: <46C601F6.5000506@livedatagroup.com>
	<29823.1187415735@sss.pgh.pa.us>

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
>   




view thread (3+ messages)

Message-ID: <46C99AB8.4000102@livedatagroup.com>
Permalink:  ../46C99AB8.4000102@livedatagroup.com/
Also on:    postgresql.org/message-id/46C99AB8.4000102@livedatagroup.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: pkalva@livedatagroup.com, tgl@sss.pgh.pa.us
  Subject: Re: Invalid String enlargement
  In-Reply-To: <46C99AB8.4000102@livedatagroup.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox