From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, "Vadim B(dot) Mikheev" <vadim(at)krs(dot)ru> |
Subject: | Re: [HACKERS] Tuple length limit |
Date: | 1999-07-04 14:20:02 |
Message-ID: | 199907041420.KAA07003@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Can someone tell me what the maximum tuple length is?
>
> I had always thought that the limit was supposed to be BLCKSZ less
> overhead.
>
> > Here is what I found with the new code. Seems it works.
> > test=> vacuum;
> > VACUUM
>
> Wasn't the complaint that started this thread something about "peculiar
> behavior" of VACUUM with big tuples? Might be wise to check VACUUM more
> closely.
We were inconsistent. Varchar and vacuum where BLCKSZ/2, while others
where BLCKSZ, of course minus overhead. The new code is consistent, and
does proper padding. I even got rid of a fudge factor in rewrite
storage by using the actual rewrite lengths.
Will be in 6.5.1.
--
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 | Bruce Momjian | 1999-07-04 14:22:45 | Re: Tuple too big |
Previous Message | Tom Lane | 1999-07-04 14:18:30 | Re: [INTERFACES] Time and microseconds? |