Re: Confronting the maximum column limitation

From: Decibel! <decibel(at)decibel(dot)org>
To: Jeff Gentry <jgentry(at)jimmy(dot)harvard(dot)edu>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Confronting the maximum column limitation
Date: 2008-08-16 19:28:37
Message-ID: E8EF2CA8-D0C7-44DD-A23D-B5BF36B0446D@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Decibel! 2008-08-16 19:31:29 Re: Changing between ORDER BY DESC and ORDER BY ASC
Previous Message Ian Harding 2008-08-16 18:22:25 Re: How to tell if a trigger is disabled