pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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?
Date: Wed, 05 Sep 2018 14:20:02 -0500
Message-ID: <87pnxrrbtp.fsf@jsievers.enova.com> (raw)
In-Reply-To: <CADyzmyyB2HY8Kzjdb0OVQXkmQSxH4Rb+C+13uupM3k5RwdmOOA@mail.gmail.com>
References: <CADyzmyyB2HY8Kzjdb0OVQXkmQSxH4Rb+C+13uupM3k5RwdmOOA@mail.gmail.com>

Mark Steben <mark.steben@drivedominion.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.consulting@comcast.net
p: 312.241.7800




view thread (4+ messages)  latest in thread

Message-ID: <87pnxrrbtp.fsf@jsievers.enova.com>
Permalink:  ../87pnxrrbtp.fsf@jsievers.enova.com/
Also on:    postgresql.org/message-id/87pnxrrbtp.fsf@jsievers.enova.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gsievers19@comcast.net, mark.steben@drivedominion.com
  Subject: Re: will this upgrade strategy work?
  In-Reply-To: <87pnxrrbtp.fsf@jsievers.enova.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox