Re: Change in db size

From: Sonam Sharma <sonams1209(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Change in db size
Date: 2019-07-17 17:32:56
Message-ID: CAM-M3T=E+ewaZaUmvCTpXcUoRYAp4VrVWNSqKFKVOrdhwC5pcw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I took the backup using pg_dump with gzip option and restored it with psql.

On Wed, Jul 17, 2019, 10:39 PM David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:

> On Wed, Jul 17, 2019 at 10:03 AM Sonam Sharma <sonams1209(at)gmail(dot)com>
> wrote:
>
>> I have restored database and the db size of source was around 55gb and
>> after restore the db size of Target is 47gb.
>>
>
> You haven't described how you restored the database but measuring size
> doesn't work because typically restoring a table causes it to be (nearly?)
> bloat free while a long running system will accumulate bloat.
>
>
>> How to confirm if restore was successful or not ?
>>
>
> A lack of error messages is a good primary indicator.
>
>
>> The table count is also same.
>>
>
> Good.
>
> Beyond that you need to decide what amount of internal data validation you
> can live with. It also depends on whether you have expected numbers based
> upon the data being restored.
>
> David J.
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2019-07-17 18:12:46 Re: Corrupt index stopping autovacuum system wide
Previous Message Tom Lane 2019-07-17 17:27:23 Re: Corrupt index stopping autovacuum system wide