On Wed, Jul 17, 2019 at 7:33 PM Sonam Sharma wrote:
>
> I took the backup using pg_dump with gzip option and restored it with psql.
It does not change the way you backed up, chances are when you
restored it the database cropped table and index bloating as already
mentioned.
The other, remote chan
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
wrote:
> On Wed, Jul 17, 2019 at 10:03 AM Sonam Sharma
> wrote:
>
>> I have restored database and the db size of source was around 55gb and
>> after restore the db size o
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 tem
On Wed, Jul 17, 2019 at 10:03 AM Sonam Sharma 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 c
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.
