From: "Joel Fradkin" <jfradkin@wazagua.com>
To: "'Michael Fuhr'" <mike@fuhr.org>
Cc: <pgsql-sql@postgresql.org>
Subject: Re: ERROR:  row is too big: size 9856, maximum size 8136
Date: Thu, 20 Jan 2005 12:20:26 -0500
Message-ID: <000601c4ff14$562cec70$797ba8c0@jfradkin>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20050120163230.GA40916@winnie.fuhr.org>

Sorry, that was the statement that caused the error.
I was creating a view that exists in the MSSQL land.
It actually joins a few tables. I can put a create statement for all the
tables used in and then create the view and re send the txt file with =
those.
I am reloading the LINUX from scratch at the moment, but as soon as I =
get
back up (be tomorrow probably as it takes over night to load the data =
from
the MSSQL server) I will email with all the pertinent information.

I am re-loading to hopefully get rid of the pg_user error I was getting =
(I
went to su postgres and created my data base that way after creating a
postgres user as root). My friend said to not create any users just =
start
the data base up (Fedora core 3) and use pgadmin to create the database.

I was following a how to convert I got off the archives, so I must of =
messed
something up.

Again thank you for the information. If it is non TOAST (sorry not sure =
what
that means; I am guessing like not part of a text field data) field =
sizes
adding up to more the 8k is there some way to produce the data set, or =
is
this a limit of Postgres in general. If I can not have all the data =
needed
in a recordset I might have to re-think using postgres is this a limit =
of
mysql also? I hate to think I have to consider staying on MSSQL as it is =
not
in our budget.

Joel Fradkin
=20
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel.  941-753-7111 ext 305
=20
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
 This email message is for the use of the intended recipient(s) and may
contain confidential and privileged information.  Any unauthorized =
review,
use, disclosure or distribution is prohibited.  If you are not the =
intended
recipient, please contact the sender by reply email and delete and =
destroy
all copies of the original message, including attachments.
=20

=20
-----Original Message-----
From: Michael Fuhr [mailto:mike@fuhr.org]=20
Sent: Thursday, January 20, 2005 11:33 AM
To: Joel Fradkin
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] ERROR: row is too big: size 9856, maximum size 8136

On Thu, Jan 20, 2005 at 08:56:12AM -0500, Joel Fradkin wrote:

> I am enclosing a text file if this is not the correct manner let me =
know
> whats best way its not a lot of lines.

The file you attached contains a view definition but it doesn't
show the underlying tables, nor the statement that resulted in the
error.  By "self-contained example" I mean enough statements that
somebody could copy them into an empty database and reproduce the
problem.

The error "row is too big: size 9856, maximum size 8136" gives a
clue at what's wrong but I'm not sure what circumstances cause it,
because the TOAST mechanism allows rows to be larger than a page.
This is just a guess, but maybe the error means that the non-TOASTABLE
data is exceeding the page size.

--=20
Michael Fuhr
http://www.fuhr.org/~mfuhr/