MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 03 May 2017 11:35:12 +0200
From: vinny <vinny@xs4all.nl>
To: Sumeet Shukla <sumeet.k.shukla@gmail.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>,
 pgsql-admin-owner@postgresql.org
Subject: Re: pg_dump backup size very less
In-Reply-To: 
 <CABUL137gBFP0_EC4RMYbzsNVXXy27H5hpD7+m0qTiNbeBh_p1A@mail.gmail.com>
References: 
 <CABUL137gBFP0_EC4RMYbzsNVXXy27H5hpD7+m0qTiNbeBh_p1A@mail.gmail.com>
Message-ID: <3910ced5eb365c3a0d3926bd7c739cc4@xs4all.nl>
User-Agent: XS4ALL Webmail
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 2017-05-03 10:19, Sumeet Shukla wrote:
> Hi,
> 
> pg_dump in custom format is creating a dump of only 29 GB for a DB of
> size 700GB. Can you please help me understand what could be the reason
> behind it.
> 
> Thanks & Regards,
> Sumeet Shukla


How did you measure that 700GB value? The total "database size" may 
include space used by indexes
and other data objects that are not included in the dump because they 
are simply re-created
when you do a restore.

The Wiki has articles on how to measure the size of your database, 
splitting up data and indexes etc.
That may help you find out where that 700GB comes from and what that 
29GB really is.

Regards,
VIncent


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin