| From: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unable to recovery due missing wal_file |
| Date: | 2016-07-04 01:50:37 |
| Message-ID: | CAJNY3iv35aSMgZ=E8P-se8csLQZJ9h7FMroeugug_-zontY=Vw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
*slave_new:* server that needs a new copy of the DB
*slave01:* streaming replication slave
*My steps are:*
*1.* ssh slave_new
*2.* Stop postgres
*3.* rm -rf /var/lib/pgsql/9.2/data/*
*4.* ssh postgres(at)slave01 'pg_basebackup --pgdata=- --format=tar
--label=slave_new --progress --host=localhost --port=5432
--username=replicator --xlog-method=stream' | tar -x --no-same-owner
*5. *Once the STEP 4 is done, copy the original postgresql.conf pg_hba.conf
recovery.conf into /var/lib/pgsql/9.2/data
*6. *Set recovery,conf with restored command.
*7. *Start Postgres
I should be able to see the DB recovering itself from the wal_files via LOGS
Is that right?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | trafdev | 2016-07-04 01:53:13 | Re: deadlock between "WITH agg_tmp AS ({sel_stmt}), upd AS ({upd_stmt}) {ins_stmt}" and pure UPDATE statements |
| Previous Message | Patrick B | 2016-07-04 01:42:36 | Re: Unable to recovery due missing wal_file |