Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA14665 for ; Thu, 12 Aug 1999 10:14:24 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA18087; Thu, 12 Aug 1999 10:12:58 -0400 (EDT) To: "Mike Field" cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Table size limit? In-reply-to: Your message of Thu, 12 Aug 1999 09:58:06 -0400 <009801bee4ca$b509d600$0200a8c0@mike> Date: Thu, 12 Aug 1999 10:12:58 -0400 Message-ID: <18085.934467178@sss.pgh.pa.us> From: Tom Lane "Mike Field" writes: > I'm inserting documents of around 80K each into a table - I split up the = > content into chunks of 8K each (I use a web interface with PHP), and = > insert the chunks into the following fields: > docid, content1, content2, content3, content4, ... , content10 That will not work --- the 8K limitation is on the total size of a tuple (record), not on the size of individual fields in it. You could make a table with fields "docid", "partno", "content" and then insert the data of a document into multiple records with the same "docid" and varying "partno". It's a pain though. I hope to see the 8K/tuple limitation go away in the next release or two. > Question: will I ever run out of space in my table? I'll have about = > 450 documents to start, then it'll grow indefinitely. =20 The total size of the table is not a problem --- you'll run out of disk space first. > My other option, from what I hear, is to just have a field for each > document with the URL of the file (either .txt or .html or whatever). Yes, you could store the text in external files and just refer to those files in the DB entries. Not a real satisfactory solution, but it might do as a workaround. A variant on this is to keep the text in "large objects" within the SQL DB, but those are hard to use; worse, they're not real efficient if you have a lot of 'em. regards, tom lane