Re: Confronting the maximum column limitation - Mailing list pgsql-general

From Decibel!
Subject Re: Confronting the maximum column limitation
Date
Msg-id E8EF2CA8-D0C7-44DD-A23D-B5BF36B0446D@decibel.org
Whole thread Raw
In response to Confronting the maximum column limitation  (Jeff Gentry <jgentry@jimmy.harvard.edu>)
Responses Re: Confronting the maximum column limitation
List pgsql-general
On Aug 12, 2008, at 3:15 PM, Jeff Gentry wrote:
> So I've seen the header file where the 1600 column limit is defined


IIRC, that limit is directly related to block size in the header, so
one possible fix is to increase block size. AFAIK anything up to 64K
blocks should be safe.

BTW, keep in mind that if you're storing anything that's a varlena
(anything that's variable length, including NUMBER) where you have
that many columns, every single varlena is going to end up toasted.
That's bound to have a *serious* performance impact.
--
Decibel!, aka Jim C. Nasby, Database Architect  decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828



Attachment

pgsql-general by date:

Previous
From: "Ian Harding"
Date:
Subject: Re: How to tell if a trigger is disabled
Next
From: Decibel!
Date:
Subject: Re: Changing between ORDER BY DESC and ORDER BY ASC