Received: from webcon.net (guru.webcon.net [216.187.106.140]) by postgresql.org (Postfix) with ESMTP id 78CF8475862 for ; Wed, 24 Apr 2002 14:10:20 -0400 (EDT) Received: from light.int.webcon.net (light.int.webcon.net [192.168.1.1]) by webcon.net (8.11.6/8.11.6) with ESMTP id g3OIANS16963; Wed, 24 Apr 2002 14:10:23 -0400 Date: Wed, 24 Apr 2002 14:10:18 -0400 (EDT) From: Ian Morgan To: "Bullock, Dempsey" Cc: pgsql-sql@postgresql.org Subject: Re: BLOB Feature Limits In-Reply-To: <9320C6656A6DD411BE4600508B6DCD6802817EDE@IMP-BWC-EXCH> Message-ID: Organization: "Webcon, Inc." MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200204/289 X-Sequence-Number: 7553 On Wed, 24 Apr 2002, Bullock, Dempsey wrote: > I'm new to PGSQL 7.2... > > I plan to create an application that stores any kind of document directly > within the database. Some of the files could be very large (1MB or larger). > Where are the limitations documented? /usr/doc/postgresql-7.2.1/html/largeobjects.html Section 2.2 says: The large object implementation breaks large objects up into "chunks" and stores the chunks in tuples in the database. A B-tree index guarantees fast searches for the correct chunk number when doing random access reads and writes. I would presume this to meant that a large object has no finite size limitation apart from the database itself exceeding disk space limits. (But I could be wrong, I'm not a PostgreSQL developer.) BTW: This should probably have been asked on the pgsql-novice list. Regards, Ian Morgan -- ------------------------------------------------------------------- Ian E. Morgan Vice President & C.O.O. Webcon, Inc. imorgan@webcon.net PGP: #2DA40D07 www.webcon.net * Customized Linux network solutions for your business * -------------------------------------------------------------------