Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cqMd0-0004bs-NL for pgsql-admin@arkaria.postgresql.org; Tue, 21 Mar 2017 16:27:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cqMd0-00018m-4p for pgsql-admin@arkaria.postgresql.org; Tue, 21 Mar 2017 16:27:22 +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 1cqMbB-0006PM-TE for pgsql-admin@postgresql.org; Tue, 21 Mar 2017 16:25:29 +0000 Received: from mail.am-soft.de ([83.218.36.120]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cqMb9-0005fr-7A for pgsql-admin@postgresql.org; Tue, 21 Mar 2017 16:25:29 +0000 Received: from tschoening-nb.fritz.box (dslb-188-102-138-175.188.102.pools.vodafone-ip.de [188.102.138.175]) by mail.am-soft.de (Postfix) with ESMTP id DE66CEED6E for ; Tue, 21 Mar 2017 17:25:23 +0100 (CET) Date: Tue, 21 Mar 2017 17:25:24 +0100 From: =?utf-8?Q?Thorsten_Sch=C3=B6ning?= Organization: AM-SoFT IT-Systeme Message-ID: <722763388.20170321172524@am-soft.de> To: "pgsql-admin@postgresql.org" Subject: Re: upgrade path from PG 8.3 to PG 9.5 In-Reply-To: References: <58AF1E37.90309@nrc-cnrc.gc.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 Guten Tag Keith, am Donnerstag, 23. Februar 2017 um 18:57 schrieben Sie: > You can go directly from 8.3 to 9.5. Just be sure and use the > pg_dump from 9.5 to generate the dump file from 8.3. Is there a specific reason for that? My current approach for upgrades was dumping the old database using the old pg_dump, uninstalling the old Postgres, installing the new one and restore from the old dump. That way I didn't accidently mix-up installations or use wrong tools or such. Did pg_dump have bugs in the past which resulted in pg_restore not being able to read the dumps? Mit freundlichen Gr=C3=BC=C3=9Fen, Thorsten Sch=C3=B6ning --=20 Thorsten Sch=C3=B6ning E-Mail: Thorsten.Schoening@AM-SoFT.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin