Re: Warm standby failover mechanism

Поиск
Список
Период
Сортировка
От Thom Brown
Тема Re: Warm standby failover mechanism
Дата
Msg-id bddc86150902250148t17acd5eeled757de0edb4ee92@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Warm standby failover mechanism  (Karsten Hilbert <Karsten.Hilbert@gmx.net>)
Ответы Re: Warm standby failover mechanism  (Thom Brown <thombrown@gmail.com>)
Список pgsql-general
2009/2/25 Karsten Hilbert <Karsten.Hilbert@gmx.net>

Think backwards: How would it automatically *dis*appear from
there. Have the secondary create it and check for existance
at regular intervals. Have the primary delete it at slightly
shorter intervals.

When the secondary finds it again after the check interval
the primary didn't delete it. Wait some more for good
measure and/or try to ping the primary some other way...


Thanks for the suggestion.  I'm wondering what the chances of such a create/delete system would have of accidentally causing failover?  Is it possible to use the archive command parameter to firstly run the pg_standby command, and follow it by a touch /tmp/pg.triggerfile by using &&?

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

Предыдущее
От: Karsten Hilbert
Дата:
Сообщение: Re: Warm standby failover mechanism
Следующее
От: Eus
Дата:
Сообщение: Can I use a query with UPDATE on its SET?