Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dovxO-0007w1-FX for pgsql-admin@arkaria.postgresql.org; Mon, 04 Sep 2017 18:18:46 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dovxO-0001gB-21 for pgsql-admin@arkaria.postgresql.org; Mon, 04 Sep 2017 18:18:46 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dovvY-0003zl-4T for pgsql-admin@postgresql.org; Mon, 04 Sep 2017 18:16:52 +0000 Received: from my.maila.biz ([138.118.35.245]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dovvQ-0007w7-V4 for pgsql-admin@postgresql.org; Mon, 04 Sep 2017 18:16:50 +0000 Received: (Haraka outbound); Mon, 04 Sep 2017 18:16:42 +0000 Authentication-Results: my.maila.biz; auth=pass (login) Received: from webmail.maila.biz (e9fe2f8a-27e0-4f92-a13d-5b2f3de0e680.cloudron [172.18.0.21]) by my.maila.biz (Haraka/2.8.13) with ESMTPA id 511D0D38-B700-43B6-AD89-6FED8D5E8072.1 envelope-from (authenticated bits=0); Mon, 04 Sep 2017 18:16:38 +0000 Mime-Version: 1.0 Date: Mon, 04 Sep 2017 18:16:37 +0000 Content-Type: multipart/alternative; boundary="--=_RainLoop_940_177346854.1504548997" X-Mailer: RainLoop/1.11.1 From: "Jean R. Franco" Message-ID: Subject: Re: pgdump and restore results in different sizes DB To: "pgsql-admin" In-Reply-To: References: <3e75543bdc093c158f050b3dfc0afe8e@maila.biz> <1758120710.400302.1504525501413@email.1and1.com> <9f30edef02a5c0f25f4c72fb191f9512@maila.biz> X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on 8cf618c304ea X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 DKIM-Signature: v=1;a=rsa-sha256;bh=wJBTpXA/7wyfPr9wbAAku1iOexdVKZm1SaVYlJalSDo=;c=relaxed/simple;d=maila.biz;h=from:subject:date:message-id:to:mime-version;s=cloudron;b=NKmUj48nauYfGZjIN5D6WY4aO8i/rUIqkBj7uhed6ESIzwQvjuhRgI7CUZ834776lS/MRTdJBcWUbC1LQIuej5qMR2twhcRP12WQ67EI4+3qUzCqX/hB0Wt+r8L+RMxlbE6BWSeNgayqtV+TgcjHbo5cK10p+MBNtlTD/kugCHQ= List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ----=_RainLoop_940_177346854.1504548997 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Thanks Keith,=0A=0AI=C2=B4m afraid that this is also going to be my probl= em!=0A=0ABest regards,=0A=0A4 de Setembro de 2017 13:02, "Keith" escreve= u:=0AOn Mon, Sep 4, 2017 at 8:36 AM, Jean R. Franco wrote:=0AHi Michael,= =0A=0AThanks for replying,=0A=0ADo you think it would be that big of a si= ze? Over 21G?=0A=0AThanks,=0AMost certainly. I've cleaned up hundreds of = gigs when a system had never done any serious bloat monitoring/cleanup be= fore. =0Ahttps://www.keithf4.com/cleaning-up-postgresql-bloat/ (https://w= ww.keithf4.com/cleaning-up-postgresql-bloat/) =0AKeith =0A4 de Setembro d= e 2017 08:45, "Michael Vitale" escreveu:=0A nice benefit of logical dump= and restore: bye bye bloat On September 4, 2017 at 7:35 AM "Jean R. Fran= co" wrote: =0AHello Everyone,=0A=0AI'm moving a postgresql server from o= ne server to another, both running versions 9.4.10=0AIt's a single large = database and I'm using pgdump to export and restoring on the new server.= =0A=0AThe thing is, on the old server the database size is 81GB, but when= I restore on the new server, it decreases to 60GB=0A=0AList of databases= =0AName | Owner | Encoding | Collate | Ctype | Access privileges | Size |= Tablespace | Description=0A------------+----------+----------+---------+= -------+-------------------+-------+------------+-------------=0Aecidade = | postgres | LATIN1 | C | C | | 60 GB | pg_default |=0A=0AI'm watching th= e whole process of restoring it and have no errors.=0AWhat could I been d= oing wrong?=0A=0AThanks, ----=_RainLoop_940_177346854.1504548997 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
T= hanks Keith,

I=C2=B4m afraid that this is also going to be my prob= lem!

Best regards,

4 de Setembro de 2017 13:02, "Keith" <= ;keith@keithf4.com> escreveu:
=
On Mon, Sep 4, 2017 at 8:36 AM, Je= an R. Franco <jfranco@maila.biz> wrote:

Hi Michael,

Thanks for replying,

Do you think it w= ould be that big of a size? Over 21G?

Thanks,

Most certa= inly. I've cleaned up hundreds of gigs when a system had never done any s= erious bloat monitoring/cleanup before.
Ke= ith
<= div style=3D"font-family: arial,sans-serif;font-size: 13px">
4 d= e Setembro de 2017 08:45, "Michael Vitale" <michaeldba@sqlexe= c.com> escreveu:

nice benefit of logical = dump and restore: bye bye bloat

On Septembe= r 4, 2017 at 7:35 AM "Jean R. Franco" <jfranco@maila.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 res= toring on the new server.

The thing is, on the old server the data= base size is 81GB, but when I restore on the new server, it decreases to = 60GB

List of databases
Name | Owner | Encoding | Collate | Ctyp= e | Access privileges | Size | Tablespace | Description
------------+-= ---------+----------+---------+-------+------------= -------+-------+------------+-------------
ecidade | postgr= es | LATIN1 | C | C | | 60 GB | pg_default |

I'm watching the whol= e process of restoring it and have no errors.
What could I been doing = wrong?

Thanks,

----=_RainLoop_940_177346854.1504548997--