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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Date: 2020-07-15 12:46:43
Message-ID: CALj2ACVzHCRnS20bOiEHaLtP5PVBENZQn4khdsSJQgOv_GM-LA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 Content-Type Size
v1-Have-SIGHUP-for-config-reload-in-logical-replicat.patch application/octet-stream 1.0 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2020-07-15 12:51:20 Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Previous Message Zhenghua Lyu 2020-07-15 12:44:38 Volatile Functions in Parallel Plans