Message-ID: <001201be4ec6$504f0680$3d063a8e@educ.sfu.ca>
From: "Gregory W Burnham" <gburnham@sfu.ca>
To: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Cc: <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] More about large objects
Date: Tue, 2 Feb 1999 08:08:46 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit

Ok, I get it.  I'd been thinking that the phrase
"we only support large objects as data stored within 
the Postgres database" meant that the lo wasn't in
an external file (which, to me, the xinv*s are).  But
I think I understand now.  Thanks Tom.


----- Original Message ----- 
From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: Gregory W Burnham <gburnham@sfu.ca>
Cc: <pgsql-interfaces@postgreSQL.org>
Sent: Tuesday, February 02, 1999 7:35 AM
Subject: Re: [INTERFACES] More about large objects


>> The postgresql docs, I posted the url didn't I?
>
>Uh, yes. I'm familiar with that document, and it is accurate, at least
>on that topic.
>
>> So according to this, the large objects are stored in the table  But
>> from what I gather from the earlier large object talk, and from my
>> own observation, postgres uses external files.  Am I deluded?  Am I
>> missing something?
>
>Yes and yes again :)
>
>The current large object implementation stores and accesses files within
>the Postgres server. All access to the files happen through the standard
>client-server connection.
>
>Internally, Postgres stores all information in files, one file per
>table, index, or large object. The large object files can be identified
>with a file prefix of "xinv_" (I think; didn't check so it may be
>something else) within the internal data storage directory
>$(PGDATA)/base/dbname/
>
>Hope this helps...
>
>                     - Tom
>