Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA17109 for ; Tue, 25 Jan 2000 12:18:29 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id MAA14017; Tue, 25 Jan 2000 12:18:21 -0500 (EST) To: Palle Girgensohn cc: Dirk Lutzebaeck , Patrik Kudo , "pgsql-sql@postgreSQL.org" Subject: Re: [SQL] Problem with large tuples. In-reply-to: <388D8903.740BB38E@partitur.se> References: <388875D0.21942465@partitur.se> <14472.32125.181522.797383@ampato.aeccom.com> <388D8903.740BB38E@partitur.se> Comments: In-reply-to Palle Girgensohn message dated "Tue, 25 Jan 2000 12:29:07 +0100" Date: Tue, 25 Jan 2000 12:18:21 -0500 Message-ID: <14014.948820701@sss.pgh.pa.us> From: Tom Lane Palle Girgensohn writes: > Dirk Lutzebaeck wrote: >> You might also need to patch vio.c. Get it from the latest snapshot... > vio.c? Can't find it the 6.5.3 sources. I guess that means I don't need to patch it, right? ;) I think he meant src/backend/access/heap/hio.c; there's a patch in there that defends against adding an oversize tuple to a relation, IIRC. regards, tom lane