Received: from siren.bio.indiana.edu (dwrice@siren.bio.indiana.edu [129.79.226.14]) by hub.org (8.8.8/8.7.5) with ESMTP id NAA23687 for ; Sat, 18 Jul 1998 13:41:08 -0400 (EDT) Received: (from dwrice@localhost) by siren.bio.indiana.edu (8.8.7/8.8.7) id MAA17247; Sat, 18 Jul 1998 12:43:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13744.56996.353223.158765@siren.bio.indiana.edu> Date: Sat, 18 Jul 1998 19:43:00 +0200 (DST) From: Danny Rice To: Rostislav Matl Cc: pgsql-sql@postgreSQL.org Subject: RE: [SQL] data larger than 8k In-Reply-To: <199807161658.SAA15445@aisa.fi.muni.cz> References: <13742.11506.902372.667917@siren.bio.indiana.edu> <199807161658.SAA15445@aisa.fi.muni.cz> X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid > > On 16-Jul-98 Danny Rice wrote: > > > > If a table element can only handle up to 8k of data what do you do if > > you need to insert larger data? > > Rostislav Matl writes: > Use large_objects - it's in man pages. Thanks, I noticed that create table test (name text, filename oid); insert into test values ( 'a file', lo_import('/tmp/afile') ); will create database files named as xinv(BigInteger) and xinx(BigInteger). When I do delete from test; or drop table test; These xin files stay around. Is there a way to have these cleaned up on delete and drop? -- Danny Rice