Fix signal handler setup for SIGHUP in the apply launcher process.
Commit 1e53fe0e70
has unified the usage of the config-file reload flag by
using the same signal handler function for the SIGHUP signal at many places
in the code. By mistake, it used the wrong SIGNAL in apply launcher
process for the SIGHUP signal handler function.
Author: Bharath Rupireddy
Reviewed-by: Dilip Kumar
Backpatch-through: 13, where it was introduced
Discussion: https://postgr.es/m/CALj2ACVzHCRnS20bOiEHaLtP5PVBENZQn4khdsSJQgOv_GM-LA@mail.gmail.com
This commit is contained in:
parent
beebbb39d9
commit
35647ea9d2
|
@ -956,7 +956,7 @@ ApplyLauncherMain(Datum main_arg)
|
|||
LogicalRepCtx->launcher_pid = MyProcPid;
|
||||
|
||||
/* Establish signal handlers. */
|
||||
pqsignal(SIGTERM, SignalHandlerForConfigReload);
|
||||
pqsignal(SIGHUP, SignalHandlerForConfigReload);
|
||||
pqsignal(SIGTERM, die);
|
||||
BackgroundWorkerUnblockSignals();
|
||||
|
||||
|
|
Loading…
Reference in New Issue