Received: from faroenet.fo ([212.55.59.140]) by hub.org (8.10.1/8.10.1) with SMTP id e7FHnKn79404 for ; Tue, 15 Aug 2000 13:49:21 -0400 (EDT) Received: (qmail 25225 invoked by uid 7719); 15 Aug 2000 18:52:41 -0000 Received: from unknown (HELO faroenet.fo) (192.168.1.21) by 192.168.1.1 with SMTP; 15 Aug 2000 18:52:41 -0000 Message-ID: <399982B7.69A41FA4@faroenet.fo> Date: Tue, 15 Aug 2000 18:49:43 +0100 From: "Poul L. Christiansen" X-Mailer: Mozilla 4.71 [en] (WinNT; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Keith Wong CC: pgsql-sql@postgresql.org Subject: Re: 8K Limit, whats the best strategy? References: <4.3.2.7.0.20000815212429.00b0eda0@mail.e-magine.com.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200008/117 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. 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.