Have SIGHUP instead of SIGTERM for config reload in logical replication launcher

Поиск
Список
Период
Сортировка
Искать
От
Bharath Rupireddy
Тема
Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Дата
Msg-id
CALj2ACVzHCRnS20bOiEHaLtP5PVBENZQn4khdsSJQgOv_GM-LA@mail.gmail.com
Список
Дерево обсуждения
Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Dilip Kumar <dilipbalaut@gmail.com>
Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Amit Kapila <amit.kapila16@gmail.com>
Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Andres Freund <andres@anarazel.de>
Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Robert Haas <robertmhaas@gmail.com>
Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher Amit Kapila <amit.kapila16@gmail.com> 
Hi,

In ApplyLauncherMain, it seems like we are having SIGTERM signal
mapped for config reload. I think we should be having SIGHUP for
SignalHandlerForConfigReload(). Otherwise we miss to take the updated
value for wal_retrieve_retry_interval in ApplyLauncherMain.

Attached is a patch having this change.

Thoughts?

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления
Предыдущее
От: Zhenghua Lyu
Дата:
Следующее
От: Dilip Kumar
Дата:
FAQ