Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Z72e3-0007K2-Un for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jun 2015 14:24:20 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1Z72e3-0002Q8-3V for pgsql-admin@arkaria.postgresql.org; Mon, 22 Jun 2015 14:24:19 +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 1Z72br-0000ZZ-R4 for pgsql-admin@postgresql.org; Mon, 22 Jun 2015 14:22:03 +0000 Received: from mailout-afa67.mailout.artfiles.de ([212.72.176.67]) by makus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Z72bp-0004zB-7D for pgsql-admin@postgresql.org; Mon, 22 Jun 2015 14:22:02 +0000 Received: from p5dc866cd.dip0.t-ipconnect.de ([93.200.102.205] helo=localhost) auth=leo@workfile.de by mailout.artfiles.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80.1) id 1Z72bm-0003wB-Fb for pgsql-admin@postgresql.org; Mon, 22 Jun 2015 16:21:58 +0200 Date: Mon, 22 Jun 2015 16:21:53 +0200 From: Rainer Leo Reply-To: Rainer Leo Organization: workfile Datenbankservice X-Priority: 3 (Normal) Message-ID: <1102220903.20150622162153@workfile.de> To: pgsql-admin@postgresql.org Subject: Re: pg_upgrade In-Reply-To: <5587E6F9.50702@afilias.info> References: <1862034146.20150622111438@workfile.de> <5587E6F9.50702@afilias.info> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Antivirus: avast! (VPS 150622-0, 22.06.2015), Outbound message X-Antivirus-Status: Clean X-Pg-Spam-Score: -1.9 (-) 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 >>> 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=20 >> pg_dump + pg_restore is "logical" (dump data and schemal to SQL=20 >> instructions). If you go that way also check pg_dumpall for dumping=20 >> the globals. >> Regards >> Jan > Also, for 1+2 you would be advised to do the pg_dump/restore using the=20 > *new* binaries (9.4), things could get tricky otherwise... > Ziggy Thanks for your help. Using the 9.4 pg_dump on the old server did not work (missing libintl-8.dll), so I used the 9.0 pg_dump. pg_restore on the new server worked fine, BUT the perfomance is lousy, for example a query that took 1732ms on the old server now takes longer than 32000ms every time on 9.4 I tuned the postgres.conf exactly like the old one, except for more RAM in some parameters. Does this mean I have to install 9.4 on the old server so I can use pg_upgrade? Rainer --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin