From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_upgrade and rsync |
Date: | 2015-01-29 17:11:04 |
Message-ID: | 20150129171104.GE4482@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 29, 2015 at 12:09:58PM -0500, Andrew Dunstan wrote:
> >>>7. shut down postgres on the replica.
> >>>
> >>>8. rsync both the old and new data directories from the master to the
> >>>replica, using the --size-only and -H hard links options. For example,
> >>>if both 9.3 and 9.4 are in /var/lib/postgresql, do:
> >>>
> >>>rsync -aHv --size-only -e ssh --itemize-changes /var/lib/postgresql/
> >>>replica-host:/var/lib/postgresql/
> >>>
> >>>9. Create a recovery.conf file in the replica's data directory with the
> >>>appropriate parameters.
> >>>
> >>>10. Start the master, then the replica
> >>>
> >>>
> >>I find steps 2 and 6 confusing.
> >For number 2, he is creating a new cluster on the master server. For
> >#6, he is just creating an empty data directory, though this is not
> >required as rsync will create the directory for you.
> >
>
>
> Then step 2 should specify that it's for the master.
Right. Josh is just listing all the steps --- the pg_upgrade docs
already have that spelled out in detail.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2015-01-29 17:37:25 | Re: pg_check_dir comments and implementation mismatch |
Previous Message | Robert Haas | 2015-01-29 17:10:58 | Re: jsonb, unicode escapes and escaped backslashes |