| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | Peter Mount <petermount(at)it(dot)maidstone(dot)gov(dot)uk> |
| Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, tim(at)perdue(dot)net, hackers(at)postgreSQL(dot)org, "Peter Mount (Home)" <peter(at)retep(dot)org(dot)uk> |
| Subject: | Re: [HACKERS] "CANNOT EXTEND" - |
| Date: | 1999-03-24 12:21:13 |
| Message-ID: | 199903241221.VAA01096@ext16.sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Is this from vacuum or pg_dump?
I'm not sure about the original message. In my case, I got
NOTICE: Can't truncate multi-segments relation tbl_mail_archive
while doing vacuum on a multi-segment relation.
However I didn't get:
ERROR: Tuple is too big: size 10024
I'm not sure if I was just lucky.
> 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).
I don't think vacuum is currently usable for a segmented relation.
> Saying that, why is it saying the tuple is too big? What is creating
> that tuple?
Seems that comes from RelationPutHeapTupleAtEnd(). It's saying
requested tuple length is too big to fit into a page. (10024 is
apparently bigger than 8192) Someting very weird is going on...
---
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D'Arcy J.M. Cain | 1999-03-24 13:47:39 | mcxt.h |
| Previous Message | Postgres mailing lists | 1999-03-24 07:37:27 | Really slow query on 6.4.2 |