From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pallav Kalva <pkalva@livedatagroup.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Invalid String enlargement
Date: Sat, 18 Aug 2007 01:42:15 -0400
Message-ID: <29823.1187415735@sss.pgh.pa.us> (raw)
In-Reply-To: <46C601F6.5000506@livedatagroup.com>
References: <46C601F6.5000506@livedatagroup.com>
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
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: tgl@sss.pgh.pa.us, pkalva@livedatagroup.com
Subject: Re: Invalid String enlargement
In-Reply-To: <29823.1187415735@sss.pgh.pa.us>
* 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