SIGHUP not received by custom bgworkers if postmaster is notified - Mailing list pgsql-hackers

From Michael Paquier
Subject SIGHUP not received by custom bgworkers if postmaster is notified
Date
Msg-id CAB7nPqSRxFhoeYnFk3im3MxV+H+mZbzLZ03FinsHo=9rPrya1w@mail.gmail.com
Whole thread Raw
Responses Re: SIGHUP not received by custom bgworkers if postmaster is notified  (Euler Taveira <euler@timbira.com>)
Re: SIGHUP not received by custom bgworkers if postmaster is notified  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Hi all,

While playing with custom background workers, I noticed that postmaster does not notify its registered bgworkers if it receives SIGHUP,
so you have to send a SIGHUP directly to the bgworker process to notify it. Signal handling is correctly done for SIGQUIT and SIGTERM for shutdown only.
Attached is a patch fixing that, I simply added a call to SignalUnconnectedWorkers in SIGHUP_handler:postmaster.c.

Regards,
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Single-argument variant for array_length and friends?
Next
From: Dimitri Fontaine
Date:
Subject: Re: [pgsql-advocacy] Call for Google Summer of Code mentors, admins