Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 6B8D49F98AB for ; Sun, 4 Nov 2007 19:04:24 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 36572-01 for ; Sun, 4 Nov 2007 19:04:18 -0400 (AST) X-Greylist: delayed 00:12:09.600759 by SQLgrey-1.7.5 Received: from boston.agmednet.com (boston.agmednet.com [74.92.47.82]) by postgresql.org (Postfix) with ESMTP id 7351B9F98A0 for ; Sun, 4 Nov 2007 19:04:17 -0400 (AST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from 71.233.123.244 ([71.233.123.244]) by agmednet-dc.boston.agmednet.local ([192.168.67.2]) with Microsoft Exchange Server HTTP-DAV ; Sun, 4 Nov 2007 22:49:13 +0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C81F34.EBEB21F8" User-Agent: Microsoft-Entourage/11.3.6.070618 Content-class: urn:content-classes:message Subject: Database size with large objects Date: Sun, 4 Nov 2007 17:49:13 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Database size with large objects thread-index: AcgfNURRgup6NosoEdy/6wAX8gFv1g== From: "Michael Goldner" To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.777 tagged_above=0 required=5 tests=AWL=-0.292, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_NUMERIC_HELO=2.067 X-Spam-Level: * X-Archive-Number: 200711/42 X-Sequence-Number: 27285 This is a multi-part message in MIME format. ------_=_NextPart_001_01C81F34.EBEB21F8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I'm running postgresql 8.1.8 on RHEL4. I have a database with a single table that includes an oid reference to = a large object. After loading 100GB of large objects using lo_import(), I find that my total database size has grown by about 270GB. What is the reason for the difference in space usage? There are about 400,000 records in the table, with each large object the same size (on average). I have autovacuum running, and had done a = vacuum --full --analyze prior to the load. Max_fsm_pages is very high (1,500,000), and the vacuum --analyze = confirms that it is sufficient. Is this just something that I have to live with? Thanks, Mike ------_=_NextPart_001_01C81F34.EBEB21F8 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Database size with large objects

I'm running postgresql 8.1.8 on RHEL4.

I have a database with a single table that includes an oid reference to = a
large object.  After loading 100GB of large objects using = lo_import(), I
find that my total database size has grown by about 270GB.  What is = the
reason for the difference in space usage?

There are about 400,000 records in the table, with each large object = the
same size (on average).  I have autovacuum running, and had done a = vacuum
--full --analyze prior to the load.

Max_fsm_pages is very high (1,500,000), and the vacuum --analyze = confirms
that it is sufficient.

Is this just something that I have to live with?

Thanks,

Mike

------_=_NextPart_001_01C81F34.EBEB21F8--