Postgres Pro
Downloads
Home   >   mailing lists

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

From Fabio Pardi
Subject Re: DB size difference after restore
Date
Msg-id 88e57f5b-2fff-a4ef-6726-dff6238f5cf7@portavita.eu
Whole thread Raw
In response to Re: DB size difference after restore  (Sonam Sharma <sonams1209@gmail.com>)
List pgsql-general
Tree view
Hi Sonam,

it is common that after an export (pg_dump) and a consecutive import, the new database uses less space than the old one.

Under some circumstances, indexes can become unbalanced or bloated, and tables bloated. And that uses more space than it should.

for the sake of trying it out: If you perform a 'vacuum full' on your old db, then the size should be very close or equal to the newly imported one.

hope it clarifies.


regards,

fabio pardi


On 03/10/18 14:51, Sonam Sharma wrote:
Hello Ben,

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


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

pgsql-general by date:

Previous
From: Sonam Sharma
Date:
Subject: Re: DB size difference after restore
Next
From: Sonam Sharma
Date:
Subject: Re: DB size difference after restore