From: Dirk Lutzebaeck <lutzeb@aeccom.com>
To: pgsql-general@postgreSQL.org
Subject: vacuum analyze: Tuple is too big (corrupts DB?)
Date: Mon, 13 Dec 1999 16:29:57 +0100 (CET)
Message-ID: <14421.4341.805191.194488@ampato.aeccom.com> (raw)
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
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-interfaces@postgresql.org
Cc: lutzeb@aeccom.com, pgsql-general@postgreSQL.org
Subject: Re: vacuum analyze: Tuple is too big (corrupts DB?)
In-Reply-To: <14421.4341.805191.194488@ampato.aeccom.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