From: Thomas Jacob <jacob@internet24.de>
To: steve@outtalimits.com.au
Cc: pgsql-admin@postgresql.org
Subject: Re: DB Dump Size
Date: Thu, 14 Aug 2008 10:30:07 +0200
Message-ID: <20080814083003.GA456@internet24.de> (raw)
In-Reply-To: <326684d8c021f4afb82f8e921f9e0c40@127.0.0.1>
References: <326684d8c021f4afb82f8e921f9e0c40@127.0.0.1>
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.
Attachments:
signature.asc (application/pgp-signature, 188B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jacob@internet24.de, steve@outtalimits.com.au
Subject: Re: DB Dump Size
In-Reply-To: <20080814083003.GA456@internet24.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox