From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Weber <j_weber@tcdi.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: 1600 column limit per table
Date: Fri, 23 May 2008 16:31:16 -0400
Message-ID: <20374.1211574676@sss.pgh.pa.us> (raw)
In-Reply-To: <48371C8A.7000206@tcdi.com>
References: <48371C8A.7000206@tcdi.com>
Mike Weber <j_weber@tcdi.com> writes:
> I ran into the 1600 column upper bound in a table and I am trying to
> assess if I can work around the limit or if I am in need of a re-design
> of my application.
You need to redesign. The 1600 limit has some slop (intentionally)
but not a lot of slop --- I think the hard maximum without breaking
compatibility with 8.1's on-disk format would be 1736.
Most people think that rows that wide are a sign of bad SQL design
anyway, which is why there's not been any interest in trying to
raise the limit. Perhaps you could collapse multiple similar columns
into an array column?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, j_weber@tcdi.com
Subject: Re: 1600 column limit per table
In-Reply-To: <20374.1211574676@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox