| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Martín Fernández <fmartin91(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PG Upgrade with hardlinks, when to start/stop master and replicas |
| Date: | 2019-02-18 20:20:53 |
| Message-ID: | 4f1d17eb6a46da084580f814cd0fd50d4ee2542c.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martín Fernández wrote:
> After reading the pg_upgrade documentation multiple times, it seems that after running pg_upgrade on the primary instance, we can't start it until we run rsync from the primary to the standby. I'm understanding this from the following section in the pg_upgrade manual page.
>
> You will not be running pg_upgrade on the standby servers, but rather rsync on the
> primary. Do not start any servers yet.
Immediately following, you can read:
If you did not use link mode, do not have or do not want to use rsync, or want an easier
solution, skip the instructions in this section and simply recreate the standby servers
once pg_upgrade completes and the new primary is running.
So this is not compulsory, it's just an efficient method to quickly get the standby
server updated.
There is nothing wrong with rebuilding the standby later.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hellmuth Vargas | 2019-02-18 20:32:31 | Re: PG Upgrade with hardlinks, when to start/stop master and replicas |
| Previous Message | Martín Fernández | 2019-02-18 20:08:59 | PG Upgrade with hardlinks, when to start/stop master and replicas |