Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1doqrN-0001Oz-3l for pgsql-admin@arkaria.postgresql.org; Mon, 04 Sep 2017 12:52:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1doqrM-0001Mu-Mg for pgsql-admin@arkaria.postgresql.org; Mon, 04 Sep 2017 12:52:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1doqrM-0001Mb-8R for pgsql-admin@postgresql.org; Mon, 04 Sep 2017 12:52:12 +0000 Received: from mout.perfora.net ([74.208.4.197]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1doqrF-0003OY-4m for pgsql-admin@postgresql.org; Mon, 04 Sep 2017 12:52:11 +0000 Received: from [192.168.3.151] ([68.84.4.95]) by mrelay.perfora.net (mreueus001 [74.208.5.2]) with ESMTPSA (Nemesis) id 0Lo01G-1dI04y3Twm-00g0DK; Mon, 04 Sep 2017 14:51:57 +0200 Content-Type: multipart/alternative; boundary=Apple-Mail-D48EFD12-8080-488D-9FA6-03945F965EEC Mime-Version: 1.0 (1.0) Subject: Re: pgdump and restore results in different sizes DB From: "Michaeldba@sqlexec.com" X-Mailer: iPad Mail (14G60) In-Reply-To: <9f30edef02a5c0f25f4c72fb191f9512@maila.biz> Date: Mon, 4 Sep 2017 08:51:54 -0400 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit Message-Id: <55858EF9-AACE-4478-809F-BB84D96FFD02@sqlexec.com> References: <1758120710.400302.1504525501413@email.1and1.com> <3e75543bdc093c158f050b3dfc0afe8e@maila.biz> <9f30edef02a5c0f25f4c72fb191f9512@maila.biz> To: "Jean R. Franco" X-Provags-ID: V03:K0:Bz2J195WfPw/v3pN8p0uzhvDC33iJA3/kSEpvRYVFNzDnQFr7F5 gunXmfqPqZa1hXM8Zjtzkzi6dNSeXUW5uqZp7079jfXdvgXbpCyA5Goem55JHB8Tq+qHLkd qUvqhhgWEgroCb3nlB90gIiq2InKkmZ+P4PU20oKwMTGqCJgH7Jqb52JDH/f7fJFIfqAFl4 nCo+w2trWVvMqsxZ9mDxw== X-UI-Out-Filterresults: notjunk:1;V01:K0:2R5T8HqpijA=:bmLpMVrM1/aV+TtMfAixoE W8Ypk9hKB7KSaHu2UGroKS4KUNepaCN7r1t9O6wNO3NqoorEtxDGFCyvdx2cM0cI9r9lyCEyx hkJX4e1DrakFf7MmWcqBEBI5PaePt9VdOTa5wtzMJc/nUUfjLVTEZ5Z4MT6QqJ1JDa3R97Zw7 5sGpvUXedE6T0Lsmj1xzPXKZFsH1qFd8isT8Cphb1ID4QFLrAETGSP7/XIFqjUsMz2STIPnJP EDx2amIYBXPT3dUkgBXoXuaYLTp07vjfo+eB8/CgV7PHLnUG13VQiSXvTj4Pj9/nIk2U4IAvx v+tUJ/pEZ07QJYEc5LgNE2dl+9MvUcBQJUQcdf1d79rtq80vq1GmTShCg3CdiO3kz23CmKGZR ZJXErqHnAqUIKkZw5WFKWRYIQQ3eNQqZFC4JrG8XM8ktF6RgUPEdLZxE7H9E5t5rhJBeTzEqp 39CrUGsykNRYlV0ecFunRlNCJqUThyaYzGATFsV9PZsu6hkPMS91kjwWeDJm84eJzMgNxixHJ n3tZT8zo5+aoI+lWkmLWO2C689NAiJHnJrnN6frut04fwKHBCcaDE29yj7PeBEUqFVmxmiiEp zN0y0HS8FwNsR8e9y+6zgu3TfDH8FxP/u7x/kFfEM/4mC7JW8TvX8nEAqhimkGxkuBAwvZ8gI Si5PXATHufdrVIYdjjVEPD6QEwMzSUL9lsXj6g9psglx4K5tZ5YYQmdapTNu1zgZZzCx4gZXH kC9xcM6SNhKNPGSLBi91xEaTzalVCy5C10I68s0oWVILTqwTYAVkHwx/ySE= 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 --Apple-Mail-D48EFD12-8080-488D-9FA6-03945F965EEC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable 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 wrote: >=20 > Hi Michael, >=20 > Thanks for replying, >=20 > Do you think it would be that big of a size? Over 21G? >=20 > Thanks, >=20 > 4 de Setembro de 2017 08:45, "Michael Vitale" esc= reveu: > nice benefit of logical dump and restore: bye bye bloat >=20 >> On September 4, 2017 at 7:35 AM "Jean R. Franco" wrot= e: >>=20 >> Hello Everyone, >>=20 >> I'm moving a postgresql server from one server to another, both running v= ersions 9.4.10 >> It's a single large database and I'm using pgdump to export and restoring= on the new server. >>=20 >> The thing is, on the old server the database size is 81GB, but when I res= tore on the new server, it decreases to 60GB >>=20 >> List of databases >> Name | Owner | Encoding | Collate | Ctype | Access privileges | Size | Ta= blespace | Description >> ------------+----------+----------+---------+-------+-------------------+= -------+------------+------------- >> ecidade | postgres | LATIN1 | C | C | | 60 GB | pg_default | >>=20 >> I'm watching the whole process of restoring it and have no errors. >> What could I been doing wrong? >>=20 >> Thanks, >=20 --Apple-Mail-D48EFD12-8080-488D-9FA6-03945F965EEC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Do select counts from all your tables i= n old and new and see if they match.

Sent from my iPad

= On Sep 4, 2017, at 8:36 AM, Jean R. Franco <jfranco@maila.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@sqlexec.com> escreveu:

nice benefit of logical dump and restore: bye bye bloat

On September 4, 2017 at 7:35 AM "Jean R. Franco" <= jfranco@maila.biz> wrote:

Hello Everyone,

I'm moving a postgresql s= erver from one server to another, both running versions 9.4.10
It's a sin= gle large database and I'm using pgdump to export and restoring on the new s= erver.

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 datab= ases
Name | Owner | Encoding | Collate | Ctype | Access privileges | Size= | Tablespace | Description
------------+----------+----------+---------+= -------+-------------------+-------+------------+-------------
ecidade | p= ostgres | LATIN1 | C | C | | 60 GB | pg_default |

I'm watching the wh= ole process of restoring it and have no errors.
What could I been doing w= rong?

Thanks,

= --Apple-Mail-D48EFD12-8080-488D-9FA6-03945F965EEC--