From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Mark Steben <mark(dot)steben(at)drivedominion(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: will this upgrade strategy work? |
Date: | 2018-09-05 19:20:02 |
Message-ID: | 87pnxrrbtp.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Mark Steben <mark(dot)steben(at)drivedominion(dot)com> writes:
> Good afternoon, team.
>
> We wish to do a postgres upgrade from 9.4 to 9.6. In order to
> minimize downtime we were thinking to do this:
> 1. bring postgres down (9.4 is on 'diskset 1')
> 2. do a physical copy of the data to 'diskset 2' (same phyxical
> server.
> 3. do an inplace pg_upgrade 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
> 4. Bring postgres up on 9.6 diskset 2
> This 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. Thanks.
>
>
> --
> Mark Steben
> Database Administrator
> @utoRevenue | Autobase
> CRM division of Dominion Dealer Solutions
> 95D Ashley Ave.
> West Springfield, MA 01089
> t: 413.327-3045
> f: 413.383-9567
>
> www.fb.com/DominionDealerSolutions
> www.twitter.com/DominionDealer
> www.drivedominion.com
>
>
>
>
>
>
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Steben | 2018-09-05 19:28:28 | Re: will this upgrade strategy work? |
Previous Message | Mark Steben | 2018-09-05 19:12:41 | will this upgrade strategy work? |