From: Jerry Sievers <gsievers19@comcast.net>
To: Mark Steben <mark.steben@drivedominion.com>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: will this upgrade strategy work?
References: 
 <CADyzmyyB2HY8Kzjdb0OVQXkmQSxH4Rb+C+13uupM3k5RwdmOOA@mail.gmail.com>
Date: Wed, 05 Sep 2018 14:20:02 -0500
In-Reply-To: 
 <CADyzmyyB2HY8Kzjdb0OVQXkmQSxH4Rb+C+13uupM3k5RwdmOOA@mail.gmail.com>
	(Mark Steben's message of "Wed, 5 Sep 2018 15:12:41 -0400")
Message-ID: <87pnxrrbtp.fsf@jsievers.enova.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Mark Steben <mark.steben@drivedominion.com> writes:

> Good afternoon, team.
>
> We wish to do a postgres upgrade from 9.4 to 9.6.=C2=A0 In order to
> minimize downtime we were thinking to do this:
> =C2=A0 1. bring postgres down (9.4 is on 'diskset 1')
> =C2=A0 2. do a physical copy of the data to 'diskset 2' (same phyxical
> server.
> =C2=A0 3.=C2=A0 do an inplace pg_upgrade=C2=A0 to 9.6 on 'diskset 2'

Note that the copy (vs link) option of pg_upgrade is non-destructive and
probably a simpler version than what you're proposing.

Whatever method you choose, best do a prior test run in a non-prod
setting to insure everything is correct.

HTH


> =C2=A0 4.=C2=A0 Bring postgres up on 9.6 diskset 2
> =C2=A0This way we have 9.4 on diskset 1 to fall back on.
>
> This would work much faster than the traditional dump restore.
>
> Any comments welcome.=C2=A0 Thanks.
>
>
> --
> Mark Steben
> =C2=A0Database Administrator
> @utoRevenue=C2=A0|=C2=A0Autobase=C2=A0
> =C2=A0 CRM division of Dominion Dealer Solutions=C2=A0
> 95D Ashley Ave.
> West Springfield, MA 01089
> t: 413.327-3045
> f: 413.383-9567
>
> www.fb.com/DominionDealerSolutions
> www.twitter.com/DominionDealer
> =C2=A0www.drivedominion.com
>
>=20=20
>
>
>
>
>
>

--=20
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
p: 312.241.7800