Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f9GL4hP80535 for ; Tue, 16 Oct 2001 17:04:44 -0400 (EDT) (envelope-from csawtell@paradise.net.nz) Received: from there (202-0-37-152.cable.paradise.net.nz [202.0.37.152]) by deborah.paradise.net.nz (Postfix) with SMTP id C4927D195F; Wed, 17 Oct 2001 10:04:40 +1300 (NZDT) Content-Type: text/plain; charset="iso-8859-1" From: Christopher Sawtell Reply-To: csawtell@paradise.net.nz To: Tom Lane , "Aasmund Midttun Godal" Subject: Re: Restricting access to Large objects Date: Wed, 17 Oct 2001 10:04:39 +1300 X-Mailer: KMail [version 1.3.1] Cc: pgsql-sql@postgresql.org References: <20011010201859.23555.qmail@ns.krot.org> <14275.1003157178@sss.pgh.pa.us> In-Reply-To: <14275.1003157178@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20011016210440.C4927D195F@deborah.paradise.net.nz> X-Archive-Number: 200110/220 X-Sequence-Number: 5175 On Tue, 16 Oct 2001 03:46, Tom Lane wrote: > "Aasmund Midttun Godal" writes: > > How can I restrict access to large objects. > > 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.