From: Tom Lane <tgl@sss.pgh.pa.us>
To: csawtell@paradise.net.nz
Cc: Aasmund Midttun Godal <aasmund@godal.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Restricting access to Large objects
Date: Tue, 16 Oct 2001 23:56:44 -0400
Message-ID: <25061.1003291004@sss.pgh.pa.us> (raw)
In-Reply-To: <20011016210440.C4927D195F@deborah.paradise.net.nz>
References: <20011010201859.23555.qmail@ns.krot.org>
<14275.1003157178@sss.pgh.pa.us>
<20011016210440.C4927D195F@deborah.paradise.net.nz>
Christopher Sawtell <csawtell@paradise.net.nz> writes:
> On Tue, 16 Oct 2001 03:46, Tom Lane wrote:
>> You can't. This is one of the many deficiencies of large objects.
> But now that the limit on row length / size has gone away, and that the new
> BYTEA type has appeared, it would seem that the need for large objects is
> redundant. Someone with more knowledge than I might like to comment.
Indeed, large objects are looking rather dinosaurian to me. TOASTed
fields seem a far more natural and flexible way of dealing with large
values.
We still have some work to do on TOASTed fields --- for example, there's
no API to read or write segments of a TOASTed field, as there is for
large objects. And it'd be nice to be able to store or retrieve BYTEA
values without worrying about quoting/escaping problems. But it makes
a lot more sense to expend effort on fixing those issues than it does
to expend effort on improving support for large objects. IMHO anyway.
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, csawtell@paradise.net.nz, aasmund@godal.com
Subject: Re: Restricting access to Large objects
In-Reply-To: <25061.1003291004@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