Received: from symcom.com (unknown [209.11.41.82]) by postgresql.org (Postfix) with ESMTP id A691E476187 for ; Wed, 27 Feb 2002 15:49:12 -0500 (EST) Received: from WorldClient [209.11.41.82] by symcom.com [209.11.41.82] with SMTP (MDaemon.v3.5.0.R) for ; Wed, 27 Feb 2002 16:07:20 -0500 Date: Wed, 27 Feb 2002 16:07:20 -0500 From: "postgresql" To: "Hunter, Ray" , pgsql-sql@postgresql.org Subject: Re: Large Objects X-Mailer: WorldClient Pro 2.2.1 In-Reply-To: <59358A738F45D51186A30008C74CE250E81448@slc-exc1.ctron.com> X-MDRemoteIP: 209.11.41.82 X-Return-Path: pgsql@symcom.com X-MDaemon-Deliver-To: pgsql-sql@postgresql.org Message-Id: <20020227204913.A691E476187@postgresql.org> X-Archive-Number: 200202/440 X-Sequence-Number: 6861 Ray, A large object is simply a large amount of data. Like a tif file or any other data that you would like to store. Personally, I would not store a large object in the database. Instead, use the locale hard disk and refer to the path to the object. Your front end would receive the path and request the OS for the file. ted -----Original Message----- From: "Hunter, Ray" To: pgsql-sql@postgresql.org Date: Wed, 27 Feb 2002 08:45:54 -0500 Subject: [SQL] Large Objects > I have been reading the user manual for largre objects in postgres. > What I > do not understand is when and why you would use them? > > Can someone point me to some good documentation on this... > > > Thanks, > > > Ray Hunter > Firmware Engineer > > ENTERASYS NETWORKS > > Phone: 801 887-9888 > Fax: 801 972-5789 > Email: rhunter@enterasys.com > www: www.enterasys.com > >