Re: DB size difference after restore - Mailing list pgsql-general

From Chris Travers
Subject Re: DB size difference after restore
Date
Msg-id CAKt_ZfvnmMKz30buB-e84S7kcpSsucAvrCDy8tJsy03ivHaiJw@mail.gmail.com
Whole thread Raw
In response to Re: DB size difference after restore  (Sonam Sharma <sonams1209@gmail.com>)
List pgsql-general


On Wed, Oct 3, 2018 at 2:59 PM Sonam Sharma <sonams1209@gmail.com> wrote:


On Wed, Oct 3, 2018 at 6:21 PM Sonam Sharma <sonams1209@gmail.com> wrote:
Hello Ben,

When we do \l+ , it is different than sourcewhen we load backup from target server.

   Backup is taken using pg_dump  and its loaded as psql db name <backup> 

It's normal that there is a size difference.

Basically you have a database you dump which may have many versions of visible rows or may have free space in the table, etc.

You take the most recent consistent backup of the visible data when you take a dump.

You create a database with only that information in it.  So one generally expects it to be smaller.  In for a db of reasonable size and load the difference may be 2x or more.

 


Regards,

Sonam


 

 


On Wed, Oct 3, 2018 at 6:17 PM Benjamin Scherrey <scherrey@proteus-tech.com> wrote:
If you're talking about space on drive then you can expect the new one to be smaller generally as it has been straight efficient writes rather than a bunch of updates and deletes which create "holes" in the physical file space.

It helps if you are more detailed as to what you've observed if you want a more specific answer. 

  - - Ben Scherrey 

On Wed, Oct 3, 2018, 7:43 PM Sonam Sharma <sonams1209@gmail.com> wrote:
I have restored the database from backup dump but the size of source and target databases are different. What can be the reason for this ?

Regards,
Sonam


--
Best Wishes,
Chris Travers

Efficito:  Hosted Accounting and ERP.  Robust and Flexible.  No vendor lock-in.

pgsql-general by date:

Previous
From: Sonam Sharma
Date:
Subject: Re: DB size difference after restore
Next
From: Floris Van Nee
Date:
Subject: GIN multi-column index