pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Johannes Truschnigg <johannes@truschnigg.info>
To: Debraj Manna <subharaj.manna@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Upgrading postgres to 10 from 9.5 using pg_upgradecluster
Date: Sat, 11 Nov 2017 12:26:35 +0100
Message-ID: <20171111112635.2cao3tmhgfvylahk@vault.lan> (raw)
In-Reply-To: <CAF6DVKPJtqap_i=CZOR0aE794CoJvoH=ZzmPUSYQWWOQ8hXs0Q@mail.gmail.com>
References: <CAF6DVKPfggzxPJ7p7pRFjLaPdoZzcnJb5kM8BWzvXXw8YKbhag@mail.gmail.com>
	<CAF6DVKPJtqap_i=CZOR0aE794CoJvoH=ZzmPUSYQWWOQ8hXs0Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Hi!

On Sat, Nov 11, 2017 at 08:02:19AM +0530, Debraj Manna wrote:
> I am testing the process of upgrading postgres to 10 from 9.5
> 
> [...]
> 
> Can someone let me know the following
> 
>    1. If there is a way I can check if the upgrade will be successful
>    before going for the actual upgrade?

Before doing a release upgrade, we usually restore the latest backup of the
cluster that's going to be upgraded to another host, and perform the planned
upgrade procedure there. For the actual upgrade, we schedule a maintenance
window, and repeaet the steps recorded during the successful test-run. This
has the added benefit that you can have confidence in your recovery/restore
process in case something goes awry.

There's no other way I know of that "simulates" performing the actual upgrade
(pg_upgrade does some pre-flight checking before it actually starts doing
work, but errors can still arise after the point of no return - which in
"link" mode means that you'll have two broken clusters, and will have to
restore from backup).


>    2. If I am using the link option in the upgrade can I still use the sudo
>    pg_dropcluster 9.5 main?

Yes.


It's a very good idea to gather experience with the workflow in a test setup,
just like you seem to be doing. You'll see that the procedure and tooling
around upgrades is very robust - but with database administration, nothing
beats a combination of diligent planning, carefulness, and experience.

-- 
with best regards:
- Johannes Truschnigg ( johannes@truschnigg.info )

www:   https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp:  johannes@truschnigg.info

Please do not bother me with HTML-email or attachments. Thank you.

Attachments:

  signature.asc (application/pgp-signature, 832B) download

view thread (2+ messages)

Message-ID: <20171111112635.2cao3tmhgfvylahk@vault.lan>
Permalink:  ../20171111112635.2cao3tmhgfvylahk@vault.lan/
Also on:    postgresql.org/message-id/20171111112635.2cao3tmhgfvylahk@vault.lan

 · 

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: johannes@truschnigg.info, subharaj.manna@gmail.com
  Subject: Re: Upgrading postgres to 10 from 9.5 using pg_upgradecluster
  In-Reply-To: <20171111112635.2cao3tmhgfvylahk@vault.lan>

* 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