Re: Promoting sync slave to master without incrementing timeline counter?

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: Promoting sync slave to master without incrementing timeline counter?
Дата
Msg-id CA+U5nMLZTEGyRcenYWKJ=ADsneHG7im_mkvSBByk_Tdp1JzbSA@mail.gmail.com
обсуждение исходный текст
Ответ на Promoting sync slave to master without incrementing timeline counter?  (David Pirotte <dpirotte@gmail.com>)
Список pgsql-general
Дерево обсуждения 
On 21 June 2012 16:10, David Pirotte <dpirotte@gmail.com> wrote:

> So, given a hard failure (i.e. power loss) of the master, `pg_ctl promote`
> provides availability more quickly, but `pg_ctl restart` provides data
> redundancy more quickly.

Not sure where this idea of "more quickly" comes from. Can you explain?


> Are there  risks associated with the `pg_ctl
> restart` approach, or is it safe to use?

PostgreSQL supports both, why do you mention just one of them as a
potential risk?

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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

Предыдущее
От: Jaime Casanova
Дата:
Сообщение: Re: Promoting sync slave to master without incrementing timeline counter?
Следующее
От: Stefan Schwarzer
Дата:
Сообщение: Re: Error message "psql: could not connect to server: No such file or directory"