|
Rather than manually syncing the master to the slave, it would be better to use pg_basebackup (http://www.postgresql.org/docs/9.1/static/app-pgbasebackup.html).
This will copy the running master to the slave, and assuming the recovery.conf is in place on the slave, it can be restarted into recovery mode almost immediately. From: pgsql-admin-owner@xxxxxxxxxxxxxx [mailto:pgsql-admin-owner@xxxxxxxxxxxxxx]
On Behalf Of Burgholzer, Robert (DEQ) I am working through getting a warm standby up and running. I have fumbled a bit, including having a non responsive standby node for a hile, which led (I think) to a big pile of “ready” files in the “pg_xlog/archive_status” directory.
My thought is that I need to start fresh, so here is the process that I envision (someone please let me know if I am making mental errors): #1 – turn off archiving on the master, restart #2 – shut down postgresql on the replicant #3 – clear the pg_xlog/archive_status/ dir, with an “rm pg_xlog/archive_status/*” command #4 – perform a fresh rsync backup of my master to my replicant #5 – bring my replicant back up into standby mode #6 – re-enable archiving on the master and restart the postmaster Thanks in advance, r.b. Robert Burgholzer Surface Water Modeler 804-869-3066 |
