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

Поиск
Список
Период
Сортировка
От Dilip Kumar
Тема Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Дата
Msg-id CAFiTN-vry=fv7fHSnEOFPu6feH_1KTXcTkYEMb-t1HOgaPw_1w@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
Список pgsql-hackers
Дерево обсуждения 
On Wed, Jul 15, 2020 at 6:17 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> 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?

Yeah, it just looks like a typo so your fix looks good to me.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

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

Предыдущее
От: Bharath Rupireddy
Дата:
Сообщение: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Следующее
От: Magnus Hagander
Дата:
Сообщение: Which SET TYPE don't actually require a rewrite