Database size with large objects

From: "Michael Goldner" <MGoldner(at)agmednet(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Database size with large objects
Date: 2007-11-04 22:49:13
Message-ID: C353B72E.17854%mgoldner@agmednet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2007-11-05 00:26:53 Re: Database size with large objects
Previous Message Tom Lane 2007-11-04 15:54:00 Re: Problems with missing OIDs