Re: Change in db size - Mailing list pgsql-general

From Sonam Sharma
Subject Re: Change in db size
Date
Msg-id CAM-M3T=E+ewaZaUmvCTpXcUoRYAp4VrVWNSqKFKVOrdhwC5pcw@mail.gmail.com
Whole thread Raw
In response to Re: Change in db size  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Change in db size  (Luca Ferrari <fluca1978@gmail.com>)
List 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.g.johnston@gmail.com> wrote:
On Wed, Jul 17, 2019 at 10:03 AM Sonam Sharma <sonams1209@gmail.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.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Corrupt index stopping autovacuum system wide
Next
From: Peter Geoghegan
Date:
Subject: Re: Corrupt index stopping autovacuum system wide