Re: pgdump and restore results in different sizes DB

From: "Michaeldba(at)sqlexec(dot)com" <Michaeldba(at)sqlexec(dot)com>
To: "Jean R(dot) Franco" <jfranco(at)maila(dot)biz>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: pgdump and restore results in different sizes DB
Date: 2017-09-04 12:51:54
Message-ID: 55858EF9-AACE-4478-809F-BB84D96FFD02@sqlexec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Do select counts from all your tables in old and new and see if they match.

Sent from my iPad

> On Sep 4, 2017, at 8:36 AM, Jean R. Franco <jfranco(at)maila(dot)biz> wrote:
>
> Hi Michael,
>
> Thanks for replying,
>
> Do you think it would be that big of a size? Over 21G?
>
> Thanks,
>
> 4 de Setembro de 2017 08:45, "Michael Vitale" <michaeldba(at)sqlexec(dot)com> escreveu:
> nice benefit of logical dump and restore: bye bye bloat
>
>> On September 4, 2017 at 7:35 AM "Jean R. Franco" <jfranco(at)maila(dot)biz> wrote:
>>
>> Hello Everyone,
>>
>> I'm moving a postgresql server from one server to another, both running versions 9.4.10
>> It's a single large database and I'm using pgdump to export and restoring on the new server.
>>
>> The thing is, on the old server the database size is 81GB, but when I restore on the new server, it decreases to 60GB
>>
>> List of databases
>> Name | Owner | Encoding | Collate | Ctype | Access privileges | Size | Tablespace | Description
>> ------------+----------+----------+---------+-------+-------------------+-------+------------+-------------
>> ecidade | postgres | LATIN1 | C | C | | 60 GB | pg_default |
>>
>> I'm watching the whole process of restoring it and have no errors.
>> What could I been doing wrong?
>>
>> Thanks,
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ramesh 2017-09-04 14:11:37 New to postgreSQL
Previous Message Jean R. Franco 2017-09-04 12:36:03 Re: pgdump and restore results in different sizes DB