pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike Field <mike@fieldco.com>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Table size limit?
Date: Thu, 12 Aug 1999 10:12:58 -0400
Message-ID: <18085.934467178@sss.pgh.pa.us> (raw)
In-Reply-To: <009801bee4ca$b509d600$0200a8c0@mike>

"Mike Field" <mike@fieldco.com> 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



view thread (2+ messages)

Message-ID: <18085.934467178@sss.pgh.pa.us>
Permalink:  ../18085.934467178@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/18085.934467178@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, mike@fieldco.com
  Subject: Re: [SQL] Table size limit?
  In-Reply-To: <18085.934467178@sss.pgh.pa.us>
  References: <009801bee4ca$b509d600$0200a8c0@mike> <18085.934467178@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox