Re: Complete Recovery 9.4.4

Поиск
Список
Период
Сортировка
От John R Pierce
Тема Re: Complete Recovery 9.4.4
Дата
Msg-id 566B3D06.1040106@hogranch.com
обсуждение исходный текст
Ответ на Complete Recovery 9.4.4  (Will McCormick <wmccormick@gmail.com>)
Ответы Re: Complete Recovery 9.4.4  (Kevin Grittner <kgrittn@gmail.com>)
Список pgsql-general
1) Stop PG <-  no, instead, execute:  select pg_start_backup();
2) Make copy of current state including PGDATA w/ pg_xlog <=  don't
backup the WAL archives, they are external to the database server, and
are written continuously.
3) Select pg_stop_backup();
4) run along until your problem happens.
5) stop postgres server
6) Cleanup PGDATA w/ pg_xlog
7) Restore backup taken in step 2, placing contents in PGDATA /w pg_xlog
8) setup a recovery.conf file specifying the desired transaction ID or
timestamp as the 'recovery_target' and the recovery command to fetch
from your archive.
9) restart postgres server and let it recover from the archives.


--
john r pierce, recycling bits in santa cruz



В списке pgsql-general по дате отправления:

Предыдущее
От: Will McCormick
Дата:
Сообщение: Complete Recovery 9.4.4
Следующее
От: Carlo Cabanilla
Дата:
Сообщение: Re: connections not getting closed on a replica