From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | maillist(at)candle(dot)pha(dot)pa(dot)us |
Cc: | Mikhail Terekhov <terekhov(at)emc(dot)com>, "Bruce Momjian"(at)candle(dot)pha(dot)pa(dot)us, root(at)candle(dot)pha(dot)pa(dot)us, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Tuple too big |
Date: | 1999-07-04 14:22:45 |
Message-ID: | 199907041422.KAA07112@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > I've encountered a strange behavior of the VACUUM ANALYZE command.
> > It seems that this command works only if the size of a text field
> > does not exceed approximately 4050 bytes! So the real limit on
> > tuple size is a half of the max tuple size. I've checked this effect
> > on Postgres 6.4.2 (Sparc Solaris 2.5.1) and Postgres 6.5 (SUSE 6.1
> > Linux, kernel 2.2.5). Is this a bug or known feature?
> > The python script used to reproduce this problem and results for
> > v6.4.2 and v6.5 are follows.
> >
>
OK, I have again written the code to allow tuples to take up a while
block, rather than the 1/2 block limit you were seeing. It consists of
a bunch of patches, so I can't send them to you, but it will be in
6.5.1, due out July 15th.
Also, the snapshot on ftp.postgresql.org has the changes too.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Mikhail Terekhov | 1999-07-04 21:05:31 | Re: [HACKERS] Tuple length limit |
Previous Message | Bruce Momjian | 1999-07-04 14:20:02 | Re: [HACKERS] Tuple length limit |