Re: pgdump and restore results in different sizes DB

On Mon, 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,
>
>
>

Most certainly. I've cleaned up hundreds of gigs when a system had never
done any serious bloat monitoring/cleanup before.

https://www.keithf4.com/cleaning-up-postgresql-bloat/

Keith

4 de Setembro de 2017 08:45, "Michael Vitale" <michaeldba(at)sqlexec(dot)com
> <%22Michael%20Vitale%22%20%3Cmichaeldba(at)sqlexec(dot)com%3E>> 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,
>
>
>