From: Thomas G. Lockhart <lockhart@alumni.caltech.edu>
To: Gregory W Burnham <gburnham@sfu.ca>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] More about large objects
Date: Tue, 02 Feb 1999 15:35:14 +0000
Message-ID: <36B71B32.7847B5EF@alumni.caltech.edu> (raw)
References: <018401be4e6c$ff8fc800$8d0835d1@bconnected.net>
> 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
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 using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lockhart@alumni.caltech.edu, gburnham@sfu.ca
Subject: Re: [INTERFACES] More about large objects
In-Reply-To: <36B71B32.7847B5EF@alumni.caltech.edu>
* 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