From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Lupo <mikelupo(at)aol(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: How to downgrade a cluster from 9.5 to 9.3 |
Date: | 2018-11-11 20:12:45 |
Message-ID: | 712579a0-724c-bfb0-3118-597f585a16a8@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 10/11/2018 16:25, Michael Lupo wrote:
> Hello all. My first post.
>
> I have a ubuntu machine that was originally running postgres 9.3. I
> installed 9.5 on that machine as well and then performed a pg_upgradecluster
> -v 9.5. 9.3 main.
> This procedure successfully moved my data from the running 9.3/main cluster,
> to the 9.5/main cluster, brought down the 9.3 running instance and then
> brought the 9.5 instance online utilizing the default ports. This was neat
> to see happen.
>
> As a back out plan, I need to know how to restore the 9.3 running instance
> if for some reason the data got corrupted in the update to 9.5.
You should be able to just shut down the 9.5 instance, switch back the
port numbers, and start the 9.3 instance.
Note that pg_upgradecluster by default uses the pg_dump method, so it's
unlikely that anything will get "corrupted" during the upgrade. It's a
more interesting consideration if you use the pg_upgrade method.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios | 2018-11-12 10:41:30 | PostgreSQL 10.5 : Logical replication timeout results in PANIC in pg_wal "No space left on device" |
Previous Message | Peter Eisentraut | 2018-11-11 20:09:07 | Re: Modules but not extensions |