Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z6z7f-0006uG-SV for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jun 2015 10:38:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Z6z7f-0004eM-5c for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jun 2015 10:38:39 +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) (envelope-from ) id 1Z6z5R-0002oC-48 for pgsql-admin@postgresql.org; Mon, 22 Jun 2015 10:36:21 +0000 Received: from mout.web.de ([212.227.15.3]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.84) (envelope-from ) id 1Z6z5O-0000fJ-Ct for pgsql-admin@postgresql.org; Mon, 22 Jun 2015 10:36:19 +0000 Received: from vm-mailsrv.lan.net ([87.152.20.113]) by smtp.web.de (mrweb004) with ESMTPSA (Nemesis) id 0LaZQd-1Ygh9c16Ap-00mJS5 for ; Mon, 22 Jun 2015 12:36:15 +0200 Received: from localhost (localhost [127.0.0.1]) by vm-mailsrv.lan.net (Postfix) with ESMTP id 4195AC81EE for ; Mon, 22 Jun 2015 12:36:13 +0200 (CEST) X-Spam-Flag: NO X-Spam-Score: -2.899 X-Spam-Level: X-Spam-Status: No, score=-2.899 tagged_above=-99.9 required=6.31 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, FREEMAIL_FROM=0.001] autolearn=ham autolearn_force=no Received: from vm-mailsrv.lan.net ([127.0.0.1]) by localhost (vm-mailsrv.lan.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UeyUi1pkOrp5 for ; Mon, 22 Jun 2015 12:36:07 +0200 (CEST) Received: from neslonek.homeunix.org (vm-webapp-ext.dmz-lan.net [192.168.0.100]) by vm-mailsrv.lan.net (Postfix) with ESMTP id 676FEF12E for ; Mon, 22 Jun 2015 12:36:07 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 22 Jun 2015 12:36:07 +0200 From: Jan Lentfer To: Subject: Re: =?UTF-8?Q?pg=5Fupgrade?= In-Reply-To: <1862034146.20150622111438@workfile.de> References: <1862034146.20150622111438@workfile.de> Message-ID: X-Sender: Jan.Lentfer@web.de User-Agent: Roundcube Webmail/0.7.2 X-Provags-ID: V03:K0:qbkXDaIGzsHcZXe3WkYNDp4C7Z7rwb34M8snUZFBzXMV/41yrMU DXVy8JdmJ2Hsa6xcGmcNgZjcT3ctuQ844b7MKx2qZYCsZ2gDMXiLF8roKbjHv7tSTW/7Hn9 h3TN83FEUjGaO7bm7nFb1hUrRRdvfCF2g6A+m0KjaULjqm3bObwDNwMsv6ii/vixRt0xnbO DbvtGbK5V5PyOz71+mpwQ== X-UI-Out-Filterresults: notjunk:1; X-Pg-Spam-Score: -3.3 (---) 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 Am 2015-06-22 11:14, schrieb Rainer Leo: > pg_upgrade Hello, > > we are still using PostgreSQL 9.0.2 on Windows Server. > > Now we are migrating to Windows Server 2012 R2 and we > would like to migrate PostgreSQL at the same time to > the current version 9.4.4-1 > > Which is the best way to migrate the data? > > 1. pg_dump on the old server > 2. pg_retore on the new server > 3. pg_upgrade on the new server > > Is this correct or is there a "best procedure" to do this? You do either 1 + 2 OR 3. pg_upgrade is binary upgrade, where as pg_dump + pg_restore is "logical" (dump data and schemal to SQL instructions). If you go that way also check pg_dumpall for dumping the globals. Regards Jan -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin