Sender: tgl@mythos.jpl.nasa.gov
Message-ID: <36B71B32.7847B5EF@alumni.caltech.edu>
Date: Tue, 02 Feb 1999 15:35:14 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Organization: Caltech/JPL
MIME-Version: 1.0
To: Gregory W Burnham <gburnham@sfu.ca>
CC: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] More about large objects
References: <018401be4e6c$ff8fc800$8d0835d1@bconnected.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> 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