To: "Joel Fradkin" <jfradkin@wazagua.com>
Cc: "'Michael Fuhr'" <mike@fuhr.org>, pgsql-sql@postgresql.org
Subject: Re: ERROR: row is too big: size 9856, maximum size 8136 
In-reply-to: <000601c4ff14$562cec70$797ba8c0@jfradkin> 
References: <000601c4ff14$562cec70$797ba8c0@jfradkin>
Comments: In-reply-to "Joel Fradkin" <jfradkin@wazagua.com>
	message dated "Thu, 20 Jan 2005 12:20:26 -0500"
Date: Thu, 20 Jan 2005 15:38:07 -0500
Message-ID: <8972.1106253487@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Joel Fradkin" <jfradkin@wazagua.com> writes:
> Sorry, that was the statement that caused the error.

Hmm.  The error is associated with trying to store an oversized row.
And CREATE VIEW doesn't store any rows ... except into system catalogs.
So the only theory I can think of is that the pg_rewrite row for the
view is exceeding 8K.  Which can't happen, because no matter how
complicated the view definition rule is, the tuple toaster should have
sprung into action and pushed the rule text out-of-line.

Could we see the results of

select * from pg_class where relname = 'pg_rewrite';

select attname,atttypid::regtype,attstorage from pg_attribute where
  attrelid = 'pg_rewrite'::regclass and attnum > 0;

7.4 should certainly be configured to have a toast table for pg_rewrite,
but maybe something went wrong during initdb on your installation.

			regards, tom lane