big database resulting in small dump - Mailing list pgsql-general

From Ilya Ivanov
Subject big database resulting in small dump
Date
Msg-id CAA=KoeJLbM=C9AYxL7xKNnam=b94dhKKPvPttqfN5RixvkWgPQ@mail.gmail.com
Whole thread Raw
Responses Re: big database resulting in small dump
Re: big database resulting in small dump
List pgsql-general
I have a 8.4 database (installed on ubuntu 10.04 x86_64). It holds Zabbix database. The database on disk takes 10Gb. SQL dump takes only 2Gb. I've gone through http://archives.postgresql.org/pgsql-general/2008-08/msg00316.php and got some hints. Naturally, the biggest table is history (the second biggest is history_uint. Together they make about 95% of total size). I've tried to perform CLUSTER on it, but seemed to be taking forever (3 hours and still not completed). So I cancelled it and went with database drop and restore. It resulted in database taking up 6.4Gb instead of 10Gb. This is a good improvement, but still isn't quite what I expect. I would appreciate some clarification.

pgsql-general by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Select Rows With Only One of Two Values [RESOLVED]
Next
From: Lonni J Friedman
Date:
Subject: Re: big database resulting in small dump