| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: finding out actual tuple size |
| Date: | 2004-02-21 00:43:30 |
| Message-ID: | 8145.1077324210@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andrew Sullivan <ajs(at)crankycanuck(dot)ca> writes:
> On Tue, Feb 17, 2004 at 03:39:25PM -0700, Linh Luong wrote:
>> 1. I have been reading and the max size of a tuple is 8K.
> That hasn't been true for ages. Use a newer PostgreSQL; any modern
> one will have the TOAST capability and won't have this limitation.
Actually it is still true, but with TOAST compression available for
individual columns it hardly ever matters anymore. If you have enough
columns in your table to be running afoul of the limit, you probably
oughta be thinking about a redesign of your database schema anyway.
But for the record: BLCKSZ is the thing to poke if you really must.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-02-21 00:51:31 | Re: pg_dump and pg_dumpall fail when trying to backup database |
| Previous Message | Bill Moran | 2004-02-21 00:33:25 | Re: Problems with plpgsql and FOR loops |