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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
