Re: 1600 Column limit..

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Williams, Travis L, NPONS" <tlw(at)att(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: 1600 Column limit..
Date: 2002-11-14 04:33:36
Message-ID: 27171.1037248416@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Williams, Travis L, NPONS" <tlw(at)att(dot)com> writes:
> Is this set in stone.. or is there somewhere you can change this.. and
> will changing it cause upgrade problems in the future..

It is not easy to make a large increase in that limit. See the comments
in src/include/access/htup.h for some of the reasons why. You'd also
need a significant increase in block size to be able to do anything
useful. (For instance, if all your columns are int4, you surely can't
fit more than 2K columns in 8K blocksize.) Finally, the system is not
very well optimized for large numbers of columns --- even if you could
physically make things fit, there are various places whose runtime is
O(N^2) in the number of columns.

I agree with the nearby comments that say you should consider a database
redesign. If extremely wide tables were a standard design technique,
we'd not have allowed these limitations to accrue...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message アムス 2002-11-14 05:36:55 Can I install 2nd set of postgresql into the same server?
Previous Message Tom Lane 2002-11-14 04:18:22 Re: Comparing strings with non-ASCII characters