Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9H42rP81420 for ; Wed, 17 Oct 2001 00:02:53 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f9H3uic25064; Tue, 16 Oct 2001 23:56:45 -0400 (EDT) To: csawtell@paradise.net.nz cc: "Aasmund Midttun Godal" , pgsql-sql@postgresql.org Subject: Re: Restricting access to Large objects 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> Comments: In-reply-to Christopher Sawtell message dated "Wed, 17 Oct 2001 10:04:39 +1300" Date: Tue, 16 Oct 2001 23:56:44 -0400 Message-ID: <25061.1003291004@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200110/226 X-Sequence-Number: 5181 Christopher Sawtell 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