From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: Large Objects
Date: Sun, 16 Sep 2001 01:56:21 -0400
Message-ID: <16936.1000619781@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.30.0109151631080.680-100000@peter.localdomain>
References: <Pine.LNX.4.30.0109151631080.680-100000@peter.localdomain>
Peter Eisentraut <peter_e@gmx.net> writes:
> We need to come up with a better reason for
> why the large object interface exists, if only because the above *used* to
> be true.
Other than backwards compatibility, the only usefulness of the LO
interface (IMHO) is that it provides random access to LO contents ---
ie, the ability to read or write small chunks of a large value.
TOAST can't completely replace LOs until we have a similar capability
for large toasted values.
regards, tom lane
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net
Subject: Re: Large Objects
In-Reply-To: <16936.1000619781@sss.pgh.pa.us>
* 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