Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 7F4509F96E0 for ; Mon, 20 Aug 2007 10:44:30 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 32941-05 for ; Mon, 20 Aug 2007 10:44:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail1.livedatagroup.com (mail1.livedatagroup.com [216.154.205.166]) by postgresql.org (Postfix) with ESMTP id AE2119F9670 for ; Mon, 20 Aug 2007 10:44:27 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mail1.livedatagroup.com (Postfix) with ESMTP id B512CB55F8; Mon, 20 Aug 2007 09:44:25 -0400 (EDT) Received: from mail1.livedatagroup.com ([192.168.3.224]) by localhost (mail1.livedatagroup.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21297-04; Mon, 20 Aug 2007 09:44:25 -0400 (EDT) Received: from [192.168.2.134] (adsl-074-228-048-194.sip.bct.bellsouth.net [74.228.48.194]) by mail1.livedatagroup.com (Postfix) with ESMTP id 06798B55D9; Mon, 20 Aug 2007 09:44:24 -0400 (EDT) Message-ID: <46C99AB8.4000102@livedatagroup.com> Date: Mon, 20 Aug 2007 09:44:24 -0400 From: Pallav Kalva User-Agent: Thunderbird 1.5.0.10 (X11/20060911) MIME-Version: 1.0 To: Tom Lane CC: pgsql-admin@postgresql.org Subject: Re: Invalid String enlargement References: <46C601F6.5000506@livedatagroup.com> <29823.1187415735@sss.pgh.pa.us> In-Reply-To: <29823.1187415735@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at livedatagroup.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/221 X-Sequence-Number: 26552 Tom Lane wrote: > Pallav Kalva 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 >