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--