Received: from ns1.engrs.org (ns1.engrs.org [216.54.29.10]) by hub.org (8.10.1/8.10.1) with ESMTP id e7LEcUT66527 for ; Mon, 21 Aug 2000 10:38:30 -0400 (EDT) Received: (from uucp@localhost) by ns1.engrs.org (8.9.3/8.9.3) id KAA01565; Mon, 21 Aug 2000 10:51:33 -0400 Received: from UNKNOWN(216.54.52.157), claiming to be "jupiter.greatbridge.com" via SMTP by ns1.engrs.org, id smtpdvXRCZc; Mon Aug 21 14:51:32 2000 Received: (from janwieck@localhost) by jupiter.greatbridge.com (8.9.3/8.9.3) id KAA02852; Mon, 21 Aug 2000 10:41:08 -0500 From: Jan Wieck Message-Id: <200008211541.KAA02852@jupiter.greatbridge.com> Subject: Re: 8K Limit, whats the best strategy? In-Reply-To: <399982B7.69A41FA4@faroenet.fo> from "Poul L. Christiansen" at "Aug 15, 2000 06:49:43 pm" To: "Poul L. Christiansen" Date: Mon, 21 Aug 2000 10:41:08 -0500 (EST) CC: Keith Wong , pgsql-sql@postgresql.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200008/215 Poul L. Christiansen wrote: > I've just split the text up (in 8 pieces), so it fits into 8K rows. But thats > only a viable solution if your text is less than a couple of 100K's. > > You could try to be a daredevil and use the Toast code, even if it's beta. But > I don't know how far the Toast project has come. TOAST is finished and will be shipped with 7.1. It's not a solution for huge items, but medium sized text up to some hundred K works fine. Jan > > Keith Wong wrote: > > > Hi everyone, > > > > Just wondering what strategies people have used to get around the 8K row > > limit in Postgres. > > If anyone has been troubled by this limitation before and has a nice > > solution around it, I would love to hear it. > > > > My application is a web-based system in which needs to store large amounts > > of text. > > The text stored needs to searchable as well. > > > > Cheers, > > Keith. > -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #