Received: from localhost (unknown [200.46.204.184]) by developer.postgresql.org (Postfix) with ESMTP id B86B22E0051 for ; Mon, 14 Apr 2008 06:22:13 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 78342-09 for ; Mon, 14 Apr 2008 06:22:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from cptwks26.careerjunction.local (unknown [196.212.105.173]) by developer.postgresql.org (Postfix) with ESMTP id 9C8762E0031 for ; Mon, 14 Apr 2008 06:22:06 -0300 (ADT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by cptwks26.careerjunction.local (Postfix) with ESMTP id EACEAB7B9F; Mon, 14 Apr 2008 11:21:59 +0200 (SAST) Message-ID: <48032237.4040604@careerjunction.co.za> Date: Mon, 14 Apr 2008 11:21:59 +0200 From: Adrian Moisey User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 To: PFC CC: pgsql-performance@postgresql.org Subject: Re: db size References: <4802F9E4.3000704@careerjunction.co.za> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/169 X-Sequence-Number: 29662 Hi > If you suspect your tables or indexes are bloated, restore your dump > to a test box. > Use fsync=off during restore, you don't care about integrity on the > test box. > This will avoid slowing down your production database. > Then look at the size of the restored database. > If it is much smaller than your production database, then you have > bloat. I have done that, and I get the following: the live one is 113G the restored one is 78G How should I get rid of the bloat? VACUUM FULL? -- Adrian Moisey Systems Administrator | CareerJunction | Your Future Starts Here. Web: www.careerjunction.co.za | Email: adrian@careerjunction.co.za Phone: +27 21 686 6820 | Mobile: +27 82 858 7830 | Fax: +27 21 686 6842