vacuum analyze: Tuple is too big (corrupts DB?)

From: Dirk Lutzebaeck <lutzeb(at)aeccom(dot)com>
To: pgsql-general(at)postgreSQL(dot)org
Subject: vacuum analyze: Tuple is too big (corrupts DB?)
Date: 1999-12-13 15:29:57
Message-ID: 14421.4341.805191.194488@ampato.aeccom.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-interfaces


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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Manuel Lemos 1999-12-13 16:28:21 Can't I create indexes on BOOL columns?
Previous Message Mark Alliban 1999-12-13 14:31:32 Re: [GENERAL] Problem in pg_hba.conf

Browse pgsql-interfaces by date

  From Date Subject
Next Message Hans Matzen 1999-12-13 16:21:02 Re: [INTERFACES] pgaccess question
Previous Message Michael Meskes 1999-12-13 14:40:44 Re: [INTERFACES] pgaccess question