Postgres Pro
Downloads
Home   >   mailing lists

Have SIGHUP instead of SIGTERM for config reload in logical replication launcher - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Date
Msg-id CALj2ACVzHCRnS20bOiEHaLtP5PVBENZQn4khdsSJQgOv_GM-LA@mail.gmail.com
Whole thread Raw
Responses Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
Tree view 
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
Attachment

pgsql-hackers by date:

Previous
From: Zhenghua Lyu
Date:
Subject: Volatile Functions in Parallel Plans
Next
From: Dilip Kumar
Date:
Subject: Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher