RE: [HACKERS] "CANNOT EXTEND" -

From: Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, tim(at)perdue(dot)net
Cc: hackers(at)postgresql(dot)org, "Peter Mount (Home)" <peter(at)retep(dot)org(dot)uk>
Subject: RE: [HACKERS] "CANNOT EXTEND" -
Date: 1999-03-23 15:15:43
Message-ID: A9DCBD548069D211924000C00D001C441A09AA@exchange.maidstone.gov.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Is this from vacuum or pg_dump?

I'm just wondering if vacuum cannot cope with a table that is >1Gb
(hence in two segments), and when cleaned down, is <1Gb (one segment).

Saying that, why is it saying the tuple is too big? What is creating
that tuple?

-----Original Message-----
From: Bruce Momjian [mailto:maillist(at)candle(dot)pha(dot)pa(dot)us]
Sent: Tuesday, March 23, 1999 2:55 PM
To: tim(at)perdue(dot)net
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] "CANNOT EXTEND" -

>
> Bruce, for the most part, I have worked around the problems with
> pg_dump.
>
> But I am getting this error now, and it is worrisome:
>
> NOTICE: Can't truncate multi-segments relation tbl_mail_archive
> ERROR: Tuple is too big: size 10024
>

Can someone comment on this? It is coming from
./backend/storage/smgr/md.c in mdtruncate(). Is this table very large?

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania
19026

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-03-23 15:47:59 Re: [HACKERS] CVS 3-22-99 \d broken?
Previous Message Bruce Momjian 1999-03-23 14:55:26 Re: [HACKERS] "CANNOT EXTEND" -