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

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Дата
Msg-id CAA4eK1JcNMyO3n2ds0=3iLdb7E2thpEz8Hf516h6HxzEho4anQ@mail.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  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Список pgsql-hackers
On Wed, Jul 15, 2020 at 6:21 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> 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.
>

+1.  I will commit this tomorrow unless someone thinks otherwise.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: renaming configure.in to configure.ac
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions