Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cqhsQ-00066w-6c for pgsql-admin@arkaria.postgresql.org; Wed, 22 Mar 2017 15:08:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cqhsP-000570-FO for pgsql-admin@arkaria.postgresql.org; Wed, 22 Mar 2017 15:08:41 +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 1cqhsO-00053C-IO for pgsql-admin@postgresql.org; Wed, 22 Mar 2017 15:08:40 +0000 Received: from host3.dynacom.ondsl.gr ([62.103.35.211] helo=smadev.internal.net) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cqhsL-0002IU-H2 for pgsql-admin@postgresql.org; Wed, 22 Mar 2017 15:08:39 +0000 Received: from smadev.internal.net (smadev [10.9.200.131]) by smadev.internal.net (8.15.2/8.15.2) with ESMTP id v2MF8YXC023095 for ; Wed, 22 Mar 2017 17:08:35 +0200 (EET) (envelope-from achill@matrix.gatewaynet.com) Subject: Re: upgrade path from PG 8.3 to PG 9.5 To: pgsql-admin@postgresql.org References: <58AF1E37.90309@nrc-cnrc.gc.ca> <722763388.20170321172524@am-soft.de> <20170321164049.GN9812@tamriel.snowman.net> <20170321165442.GO9812@tamriel.snowman.net> <58D2231B.8050405@matrix.gatewaynet.com> From: Achilleas Mantzios Message-ID: <58D29372.5090900@matrix.gatewaynet.com> Date: Wed, 22 Mar 2017 17:08:34 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------010009000009000201030501" 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 This is a multi-part message in MIME format. --------------010009000009000201030501 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 22/03/2017 16:47, Keith wrote: > > We used pg_upgrade recently for migrating from 8.3 -> *9.4 (the last version which supports 8.3)*, and it went nice. We had some custom functions in C, and pg_upgrade is a disciplined way to deal > with the migration > > I would be curious how that worked since the documentation states the old version must be at least 8.4.7 for pg_upgrade to work. You missed the 9.4 part : https://www.postgresql.org/docs/9.4/static/pgupgrade.html "pg_upgrade supports upgrades from 8.3.X and later" Then they can pg_upgrade from 9.4 -> 9.6 much easier. > > https://www.postgresql.org/docs/9.6/static/pgupgrade.html > > Just checked this with 8.3.22 and confirmed the binary won't even let you run it. > > $ pg_upgrade -b /opt/pgsql8323/bin -B /opt/pgsql962/bin -c -d /opt/pgdata/83 -D /opt/pgdata/83upgrade > Performing Consistency Checks > ----------------------------- > Checking cluster versions > This utility can only upgrade from PostgreSQL version 8.4 and later. > Failure, exiting > > Not trying to be pedantic, but don't want to lead someone down a road that won't work properly. > > Keith-- > Achilleas Mantzios > IT DEV Lead > IT DEPT > Dynacom Tankers Mgmt > > > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org ) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > -- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt --------------010009000009000201030501 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
On 22/03/2017 16:47, Keith wrote:

We used pg_upgrade recently for migrating from 8.3 -> 9.4 (the last version which supports 8.3), and it went nice. We had some custom functions in C, and pg_upgrade is a disciplined way to deal with the migration

I would be curious how that worked since the documentation states the old version must be at least 8.4.7 for pg_upgrade to work.

You missed the 9.4 part : https://www.postgresql.org/docs/9.4/static/pgupgrade.html
"pg_upgrade supports upgrades from 8.3.X and later"

Then they can pg_upgrade from 9.4 -> 9.6 much easier.

Just checked this with 8.3.22 and confirmed the binary won't even let you run it.

$ pg_upgrade -b /opt/pgsql8323/bin -B /opt/pgsql962/bin -c -d /opt/pgdata/83 -D /opt/pgdata/83upgrade
Performing Consistency Checks
-----------------------------
Checking cluster versions                                  
This utility can only upgrade from PostgreSQL version 8.4 and later.
Failure, exiting
 
Not trying to be pedantic, but don't want to lead someone down a road that won't work properly.

Keith--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt




--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
--------------010009000009000201030501--