Received: from k3.aeccom.com (IDENT:root@gate1.aeccom.com [193.158.11.51])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA02792
	for <pgsql-general@postgreSQL.org>;
	Mon, 13 Dec 1999 10:30:06 -0500 (EST)
	(envelope-from lutzeb@aeccom.com)
Received: from ampato.aeccom.com (IDENT:root@ampato.aeccom.com [192.168.0.11])
	by k3.aeccom.com (8.9.3/8.9.3) with ESMTP id QAA08764;
	Mon, 13 Dec 1999 16:30:01 +0100
Received: (from lutzeb@localhost)
	by ampato.aeccom.com (8.9.3/8.9.3) id QAA01840;
	Mon, 13 Dec 1999 16:30:01 +0100
From: Dirk Lutzebaeck <lutzeb@aeccom.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14421.4341.805191.194488@ampato.aeccom.com>
Date: Mon, 13 Dec 1999 16:29:57 +0100 (CET)
To: pgsql-general@postgreSQL.org
Subject: vacuum analyze: Tuple is too big (corrupts DB?)
X-Mailer: VM 6.71 under 21.1 (patch 4) "Arches" XEmacs Lucid


Hello,

when I vacuum analyze my db (6.5.3 on Linux) I cannot access
some data afterwards because the vacuum terminates with

ERROR:  Tuple is too big: size 8596

I did pg_dump -o and read in back again, still the same error. 

Eg. accessing data after vacuum results in

SELECT envpart_map.*,
       envpart_map.oid AS recioid,
       member.*,
       member.oid AS memoid
       WHERE envpart_map.member=member.oid
       AND envpart_map.role > 0
       AND envpart_map.envelope IN (1072343,1073358,1074472,1073722,14235
82)': pqReadData() -- backend closed the channel unexpectedly.


Where can I get on from here?

Dirk