Subject: Re: Column limits in table/ views
From: Rod Taylor <rbt@rbt.ca>
To: "A.M." <agentm@cmu.edu>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <945001F0-986A-11D7-AAB2-0030657192DA@cmu.edu>
References: <945001F0-986A-11D7-AAB2-0030657192DA@cmu.edu>
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-nx9+ecAPm0WoyV/kB+f6"
Organization: 
Message-Id: <1054993688.23997.26.camel@jester>
Mime-Version: 1.0
Date: 07 Jun 2003 09:48:08 -0400

--=-nx9+ecAPm0WoyV/kB+f6
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2003-06-06 at 18:02, A.M. wrote:
> I have 560 columns of NUMERIC(10,14). To not run up against max column=20
> restraints, I split the information into two tables. Does the column=20
> limit on tables imply the same limit for views or selects or could I=20
> potentially select a row across both tables and make a view that hides=20
> the split?

The limit is documented as having to do with the size of a block.  The
largest a single row can become is 8k with primitive types (text, and
other variable length types will 'overflow' into another area -- see
TOAST).

Selects should be able to return more columns than that.  Both views and
tables create a ROW TYPE to represent it, which is where the limitation
is.  Thus, I would not expect you to be able to create a view.

--=20
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

--=-nx9+ecAPm0WoyV/kB+f6
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQA+4e0Y6DETLow6vwwRApx0AJwNCrgsLux5HpBMRbUnmXNaFpUZYQCfSwOt
t8GIrHTJbMURF4nvQ52Mwm0=
=Yqiy
-----END PGP SIGNATURE-----

--=-nx9+ecAPm0WoyV/kB+f6--