Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 41F1A9F9AD3 for ; Sat, 18 Aug 2007 02:42:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 01241-05 for ; Sat, 18 Aug 2007 02:42:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id C91F09F9AD8 for ; Sat, 18 Aug 2007 02:42:17 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l7I5gFC8029824; Sat, 18 Aug 2007 01:42:15 -0400 (EDT) To: Pallav Kalva cc: pgsql-admin@postgresql.org Subject: Re: Invalid String enlargement In-reply-to: <46C601F6.5000506@livedatagroup.com> References: <46C601F6.5000506@livedatagroup.com> Comments: In-reply-to Pallav Kalva message dated "Fri, 17 Aug 2007 16:15:50 -0400" Date: Sat, 18 Aug 2007 01:42:15 -0400 Message-ID: <29823.1187415735@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/211 X-Sequence-Number: 26542 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: > 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