MIME-Version: 1.0
Date: Fri, 15 Aug 2008 09:26:18 +1000
From: <steve@outtalimits.com.au>
To: Thomas Jacob <jacob@internet24.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: DB Dump Size
In-Reply-To: <20080814083003.GA456@internet24.de>
References: <326684d8c021f4afb82f8e921f9e0c40@127.0.0.1>
	<20080814083003.GA456@internet24.de>
Message-ID: <02f4fac97d67bb4a1cee604724c8d62d@127.0.0.1>
User-Agent: RoundCube Webmail/0.2a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

G'day,

I am just running a straight pg_dump with no options.
With the -Fc option the DB size is reduced to about: 700MB

Is the -Fc a compressed format? Are there any limitations or side effects
to using this output, is it slower?? etc etc. Can this output be restored
via the normal method of: psql dbname < sql.dump

Thanks.
Steve


On Thu, 14 Aug 2008 10:30:07 +0200, Thomas Jacob <jacob@internet24.de>
wrote:
> On Thu, Aug 14, 2008 at 12:06:53PM +1000, steve@outtalimits.com.au wrote:
>> Hi all,
>> 
>> I am curious as to why a pg dump of database "name" is 2.9gig. But is
>> measured at 1.66gig by:
>> SELECT pg_database_size(pg_database.datname) AS db_size FROM pg_database
>> WHERE pg_database.datname='name' ;
>> 
>> This dump was about 1 gig around 12 months ago.
> 
> Which options do you use for pg_dump? And what version of PosgreSQL are
> you running?
> 
> In general it's not that strange for an uncompressed
> dump to be larger than the database size, plain SQL
> dumps are much less space efficient than a DBMS can
> be when it stores the data on disk. But of course, there
> also indices to consider.
> 
> Have you tried pg_dump -Fc?
> 
>> I am performing a monthly vacuum full on the database and a nightly
> vacuum
>> all
> 
> That should only impact the pg_database_size.