From jfradkin@wazagua.com Wed Jan 19 20:47:47 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B1B1F3A4370 for ; Wed, 19 Jan 2005 20:47:47 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68956-01 for ; Wed, 19 Jan 2005 20:47:35 +0000 (GMT) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by svr1.postgresql.org (Postfix) with ESMTP id 054293A430D for ; Wed, 19 Jan 2005 20:47:35 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out007.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050119204735.BYNV21228.out007.verizon.net@jfradkin> for ; Wed, 19 Jan 2005 14:47:35 -0600 From: "Joel Fradkin" To: Subject: ERROR: row is too big: size 9856, maximum size 8136 Date: Wed, 19 Jan 2005 15:50:30 -0500 Message-ID: <000001c4fe68$85cb3ec0$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4FE3E.9CF536C0" X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [66.15.127.235] at Wed, 19 Jan 2005 14:47:31 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.077 tagged_above=0 required=5 tests=AWL, HTML_MESSAGE, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200501/152 X-Sequence-Number: 19940 This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4FE3E.9CF536C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I get ERROR: row is too big: size 9856, maximum size 8136 when inserting a view? Help Joel Fradkin Wazagua, LLC 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 jfradkin@wazagua.com www.wazagua.com Powered by Wazagua Providing you with the latest Web-based technology & advanced tools. C 2004. WAZAGUA, LLC. All rights reserved. WAZAGUA, LLC 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. ------=_NextPart_000_0001_01C4FE3E.9CF536C0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I get ERROR:  row is too big: size 9856, maximum = size 8136 when inserting a view?

 

Help

 

Joel Fradkin

 

Wazagua, LLC
2520 Trailmate Dr
Sarasota, Florida = 34243
Tel.  941-753-7111 ext 305

 

jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced = tools.
© 2004. WAZAGUA, LLC. All rights reserved. WAZAGUA, LLC
 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.

 


 

 

------=_NextPart_000_0001_01C4FE3E.9CF536C0-- From mike@fuhr.org Thu Jan 20 03:01:24 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5E5BB3A45E2 for ; Thu, 20 Jan 2005 03:01:24 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02789-04 for ; Thu, 20 Jan 2005 03:01:14 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id D44C63A45BD for ; Thu, 20 Jan 2005 03:01:17 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.1/8.13.1) with ESMTP id j0K31EVo005854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 19 Jan 2005 20:01:17 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.1/8.13.1) with ESMTP id j0K31Edd097202; Wed, 19 Jan 2005 20:01:14 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.1/8.13.1/Submit) id j0K31DBw097201; Wed, 19 Jan 2005 20:01:13 -0700 (MST) (envelope-from mfuhr) Date: Wed, 19 Jan 2005 20:01:13 -0700 From: Michael Fuhr To: Joel Fradkin Cc: pgsql-sql@postgresql.org Subject: Re: ERROR: row is too big: size 9856, maximum size 8136 Message-ID: <20050120030113.GA97108@winnie.fuhr.org> References: <000001c4fe68$85cb3ec0$797ba8c0@jfradkin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c4fe68$85cb3ec0$797ba8c0@jfradkin> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/155 X-Sequence-Number: 19943 On Wed, Jan 19, 2005 at 03:50:30PM -0500, Joel Fradkin wrote: > I get ERROR: row is too big: size 9856, maximum size 8136 when inserting a > view? Could you post the smallest possible self-contained example that demonstrates this behavior? What version of PostgreSQL are you using? -- Michael Fuhr http://www.fuhr.org/~mfuhr/ From jfradkin@wazagua.com Thu Jan 20 13:53:28 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A97D53A4269 for ; Thu, 20 Jan 2005 13:53:28 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 97469-09 for ; Thu, 20 Jan 2005 13:53:12 +0000 (GMT) Received: from out008.verizon.net (out008pub.verizon.net [206.46.170.108]) by svr1.postgresql.org (Postfix) with ESMTP id 20CCA3A4766 for ; Thu, 20 Jan 2005 13:53:13 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out008.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050120135313.LDMH17379.out008.verizon.net@jfradkin>; Thu, 20 Jan 2005 07:53:13 -0600 From: "Joel Fradkin" To: "'Michael Fuhr'" Cc: Subject: Re: ERROR: row is too big: size 9856, maximum size 8136 Date: Thu, 20 Jan 2005 08:56:12 -0500 Message-ID: <002901c4fef7$ce1c60c0$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_002A_01C4FECD.E54658C0" In-Reply-To: <20050120030113.GA97108@winnie.fuhr.org> X-Authentication-Info: Submitted using SMTP AUTH at out008.verizon.net from [66.15.127.235] at Thu, 20 Jan 2005 07:53:12 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.076 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200501/167 X-Sequence-Number: 19955 This is a multi-part message in MIME format. ------=_NextPart_000_002A_01C4FECD.E54658C0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. ServerVersion: 07.03.0200 PostgreSQL 7.4.6 on i386-redhat-linux-gnu, compiled by GCC i386-redhat-linux-gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2 ERROR: row is too big: size 9856, maximum size 8136 Joel Fradkin Wazagua, LLC 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 jfradkin@wazagua.com www.wazagua.com Powered by Wazagua Providing you with the latest Web-based technology & advanced tools. C 2004. WAZAGUA, LLC. All rights reserved. WAZAGUA, LLC 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. -----Original Message----- From: Michael Fuhr [mailto:mike@fuhr.org] Sent: Wednesday, January 19, 2005 10:01 PM To: Joel Fradkin Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] ERROR: row is too big: size 9856, maximum size 8136 On Wed, Jan 19, 2005 at 03:50:30PM -0500, Joel Fradkin wrote: > I get ERROR: row is too big: size 9856, maximum size 8136 when inserting a > view? Could you post the smallest possible self-contained example that demonstrates this behavior? What version of PostgreSQL are you using? -- Michael Fuhr http://www.fuhr.org/~mfuhr/ ------=_NextPart_000_002A_01C4FECD.E54658C0 Content-Type: text/plain; name="rowtobigerror.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="rowtobigerror.txt" CREATE OR REPLACE VIEW thenetworkcallbackview as select i.clientnum, i.incidentid, incidentnum, incidenttypeid, = incidentdate, subjectid, subjecttypeid, locationid, = suspectedactivity.value as description, situation, policenotified, = injuries,=20 injurednum, injuriesdescription, propertydamage, = damagelevelid, incidentreport, i.transfered, i.transftypeid, = i.transfdate, i.transfbyid, i.transfnum,=20 lastmodified, createdbyid,i.isdeleted, = workflowstatus, cashloss, merchloss, totloss, markettypeid, = typeofweaponid, alarmid, cameraid,=20 escalated, transcount, orgcalldate_time, = anoncaller, callernamefirst as firstname, callernamelast as lastname, = callernamefirst || ' ' || callernamelast as callernamelast, callertype, = callertitle,=20 callerphone, callerext, callerbesttimetocall, = calleremail, clientname, location, dba, address1, address2, city, state, = zip, country, phone, ext,=20 abuselocation, casesource.value as hoiwincdknown, = supportdocsavailable, next24hours, nextwhen, nextwhere, howhotlineknown, = interviewernotes,=20 clientinstructions, case=20 when i.statusid is null then 'none' when i.statusid =3D 1 then 'open' when i.statusid =3D 2 then 'closed' end as status,i.assignedto, cb.callbackdate, substring(cb.callbacknotes,1,20) as callbacknotes from tblincident i inner join tblincidentcallback cb on i.incidentnum =3D cb.incidentid = and i.clientnum =3D cb.clientnum left outer join tblcasesource casesource on i.inccasesourceid =3D = casesource.id and (i.clientnum=3Dcasesource.clientnum) left outer join tblsuspectedactivity suspectedactivity on = i.incsuspectedactivityid =3D suspectedactivity.id and = (i.clientnum=3Dsuspectedactivity.clientnum); ------=_NextPart_000_002A_01C4FECD.E54658C0-- From mike@fuhr.org Thu Jan 20 16:32:39 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CCB0E3A45AA for ; Thu, 20 Jan 2005 16:32:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23225-05 for ; Thu, 20 Jan 2005 16:32:36 +0000 (GMT) Received: from tigger.fuhr.org (tigger.fuhr.org [63.214.45.158]) by svr1.postgresql.org (Postfix) with ESMTP id 570813A1CF7 for ; Thu, 20 Jan 2005 16:32:35 +0000 (GMT) Received: from winnie.fuhr.org (winnie.fuhr.org [10.1.0.1]) by tigger.fuhr.org (8.13.1/8.13.1) with ESMTP id j0KGWVrL006771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 20 Jan 2005 09:32:33 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: from winnie.fuhr.org (localhost [127.0.0.1]) by winnie.fuhr.org (8.13.1/8.13.1) with ESMTP id j0KGWUBJ041011; Thu, 20 Jan 2005 09:32:30 -0700 (MST) (envelope-from mfuhr@winnie.fuhr.org) Received: (from mfuhr@localhost) by winnie.fuhr.org (8.13.1/8.13.1/Submit) id j0KGWUxQ041010; Thu, 20 Jan 2005 09:32:30 -0700 (MST) (envelope-from mfuhr) Date: Thu, 20 Jan 2005 09:32:30 -0700 From: Michael Fuhr To: Joel Fradkin Cc: pgsql-sql@postgresql.org Subject: Re: ERROR: row is too big: size 9856, maximum size 8136 Message-ID: <20050120163230.GA40916@winnie.fuhr.org> References: <20050120030113.GA97108@winnie.fuhr.org> <002901c4fef7$ce1c60c0$797ba8c0@jfradkin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002901c4fef7$ce1c60c0$797ba8c0@jfradkin> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.003 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/171 X-Sequence-Number: 19959 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. -- Michael Fuhr http://www.fuhr.org/~mfuhr/ From jfradkin@wazagua.com Thu Jan 20 17:17:39 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9E28F3A1CF7 for ; Thu, 20 Jan 2005 17:17:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47805-09 for ; Thu, 20 Jan 2005 17:17:29 +0000 (GMT) Received: from out011.verizon.net (out011pub.verizon.net [206.46.170.135]) by svr1.postgresql.org (Postfix) with ESMTP id 724D43A4885 for ; Thu, 20 Jan 2005 17:17:28 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out011.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050120171727.MEDE4717.out011.verizon.net@jfradkin>; Thu, 20 Jan 2005 11:17:27 -0600 From: "Joel Fradkin" To: "'Michael Fuhr'" Cc: 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> X-Authentication-Info: Submitted using SMTP AUTH at out011.verizon.net from [66.15.127.235] at Thu, 20 Jan 2005 11:17:26 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.082 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200501/177 X-Sequence-Number: 19965 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/ From dev@archonet.com Thu Jan 20 17:44:26 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 242323A4729 for ; Thu, 20 Jan 2005 17:44:26 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 50726-08 for ; Thu, 20 Jan 2005 17:44:10 +0000 (GMT) Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by svr1.postgresql.org (Postfix) with ESMTP id 3B1653A48AB for ; Thu, 20 Jan 2005 17:44:10 +0000 (GMT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-31.mail.demon.net with esmtp (Exim 4.42) id 1CrgKn-0004md-5v; Thu, 20 Jan 2005 17:43:06 +0000 Received: from [192.168.1.17] (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 0B15E170C3; Thu, 20 Jan 2005 17:44:08 +0000 (GMT) Message-ID: <41EFEDE9.1020700@archonet.com> Date: Thu, 20 Jan 2005 17:44:09 +0000 From: Richard Huxton User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joel Fradkin Cc: 'Michael Fuhr' , pgsql-sql@postgresql.org Subject: Re: ERROR: row is too big: size 9856, maximum size 8136 References: <000601c4ff14$562cec70$797ba8c0@jfradkin> In-Reply-To: <000601c4ff14$562cec70$797ba8c0@jfradkin> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.074 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/179 X-Sequence-Number: 19967 Joel Fradkin wrote: > 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. There are probably RPMs for 8.0 available by now. Might be worth going to that from the start, rather than upgrading later. > 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. Well, that's a lot of non-text columns to breach 8kB. It is a definite limit, but you shouldn't see it until you have hundreds of columns. If you can post the table definitions along with the view definition, that should let people see if they can reproduce the problem. -- Richard Huxton Archonet Ltd From tgl@sss.pgh.pa.us Thu Jan 20 20:38:37 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 783303A492D for ; Thu, 20 Jan 2005 20:38:37 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72575-04 for ; Thu, 20 Jan 2005 20:38:27 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6148D3A4927 for ; Thu, 20 Jan 2005 20:38:27 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j0KKc7Qp008973; Thu, 20 Jan 2005 15:38:07 -0500 (EST) To: "Joel Fradkin" Cc: "'Michael Fuhr'" , 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" 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 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/180 X-Sequence-Number: 19968 "Joel Fradkin" 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 From jfradkin@wazagua.com Thu Jan 20 21:05:55 2005 X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id F26203A1CF7 for ; Thu, 20 Jan 2005 21:05:55 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76148-04 for ; Thu, 20 Jan 2005 21:05:50 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by svr1.postgresql.org (Postfix) with ESMTP id C5F143A4938 for ; Thu, 20 Jan 2005 21:05:50 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050120210550.MUJZ28025.out001.verizon.net@jfradkin>; Thu, 20 Jan 2005 15:05:50 -0600 From: "Joel Fradkin" To: "'Tom Lane'" Cc: "'Michael Fuhr'" , Subject: Re: ERROR: row is too big: size 9856, maximum size 8136 Date: Thu, 20 Jan 2005 16:08:49 -0500 Message-ID: <000901c4ff34$3de4bec0$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable In-reply-to: <8972.1106253487@sss.pgh.pa.us> X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [66.15.127.235] at Thu, 20 Jan 2005 15:05:49 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.081 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200501/181 X-Sequence-Number: 19969 Could very well be an install issue I was getting errors trying to see template1. I am in the process of re-installing Linux and will let you = know if I still have the error what I get from the select you asked me to = run. I appreciate everyones help.=20 If anyone has an interest in the .net utility I wrote to pull the tables schema and data let me know. I used SQLDMO to have the script text = available and then converted it to postgres syntax. I automated the creation and = move of the data including the text fields(it runs a little slow as it does a read and write at a table row level, but this seemed the best way to get = the text fields to move over). The views and procedures I am afraid I will = have to use the list all views syntax and convert by hand as stuff like left = and datediff would be difficult to auto-convert. I did create a left and = right function but could see a performance hit for each use of function and = feel it will be better to just convert the SQL (the hit was only milisecs on first number I guess the prepare part, but still might as well have it = be as fast as possible). 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: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20 Sent: Thursday, January 20, 2005 3:38 PM To: Joel Fradkin Cc: 'Michael Fuhr'; pgsql-sql@postgresql.org Subject: Re: [SQL] ERROR: row is too big: size 9856, maximum size 8136=20 "Joel Fradkin" 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 =3D 'pg_rewrite'; select attname,atttypid::regtype,attstorage from pg_attribute where attrelid =3D '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