| From: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
|---|---|
| To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
| Cc: | Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Help on recovering my standby |
| Date: | 2016-06-22 21:42:10 |
| Message-ID: | CAJNY3isS3ZL1Mr-JVrWpeNy-ZSvdYn25L5D2PC1Yr3vs2kUsyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I had the same issue... A slave server had missing wal_files... and it
wasn't synced.
I had to re-sync all the DB, by running the pg_basebackup command....
So.. basically, what I did is:
1 - Ensure that the wal_files are being inserted into the slave
2 - Backup the recovery.conf, postgresql.conf and pg_hba.conf
3 - Delete all the current data folder, by doing: rm -rf
/var/lib/pgsql/9.2/data/*
4 - Running the pg_basebackup command to re-sync the DB from another slave
to the slave that I wanna fix
5 - Replace the .conf backup files into the new data folder
6 - Start postgres
And it worked nice....
Patrick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Vanasco | 2016-06-22 22:27:58 | Re: optimizing a query |
| Previous Message | Bill Moran | 2016-06-22 20:56:57 | Re: Protect a table against concurrent data changes while allowing to vacuum it |