Re: Disable Streaming Replication without restarting either master or slave

Поиск
Список
Период
Сортировка
От Raghavendra
Тема Re: Disable Streaming Replication without restarting either master or slave
Дата
Msg-id CA+h6Ahh5pTnJeeZ5bd063+V84tWdRWWZaMuwm7g9JMLRdbxX6w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Disable Streaming Replication without restarting either master or slave  (Sergey Konoplev <gray.ru@gmail.com>)
Ответы Re: Disable Streaming Replication without restarting either master or slave  (Fujii Masao <masao.fujii@gmail.com>)
Список pgsql-general
Дерево обсуждения
> Since stopping or restarting the postgres servers would involve complete
> invalidation of the connection pool [Java/JEE app server pool] that may take
> a few minutes before the application becomes usable, it would be great if
> there is a way we can disable replication [for maintenance reasons like
> applying patches or upgrades, etc].


I think even applying patches or upgrades needs restart.


3. send SIGTERM signal to currently-running walsender process, e.g., by
   "select pg_terminate_backend(pid) from pg_stat_replication".
 
Will it be helpful here sending SIGINT instead of killing ?

---
Regards,
Raghavendra
EnterpriseDB Corporation

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

Предыдущее
От: Chris Angelico
Дата:
Сообщение: Re: Interval Division Workaround Suggestions (sub-day intervals only)?
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: Disable Streaming Replication without restarting either master or slave