Re: [External] Change in db size

From: Vijaykumar Jain <vjain(at)opentable(dot)com>
To: Sonam Sharma <sonams1209(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [External] Change in db size
Date: 2019-07-17 17:15:52
Message-ID: CAE7uO5gqL19=OB+umkz8quVPzbt4es68vqLYh_6Apts+z6WFpQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I guess the restore cleared the bloat from the table.
\dt+
\di+
If you run the above commands from the terminal, you would see diff in
sizes of the. objects.
Also querying pg_stat_all_tables you might see “dead” tuples in old tables
which would have cleaned up now.
Also if there were any large temp objects or queries using temp files would
have cleared and hence reclaimed disk.
If none of these are true, then I guess experts would pitch in.

On Wed, 17 Jul 2019 at 10:33 PM 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.
>
> How to confirm if restore was successful or not ?
> The table count is also same.
>
--

Regards,
Vijay

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2019-07-17 17:18:19 Re: Corrupt index stopping autovacuum system wide
Previous Message David G. Johnston 2019-07-17 17:09:42 Re: Change in db size