| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | SIGHUP not received by custom bgworkers if postmaster is notified |
| Date: | 2013-03-21 08:06:24 |
| Message-ID: | CAB7nPqSRxFhoeYnFk3im3MxV+H+mZbzLZ03FinsHo=9rPrya1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| 20130321_bgworker_sighup.patch | application/octet-stream | 502 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2013-03-21 08:29:29 | Re: [HACKERS] Call for Google Summer of Code mentors, admins |
| Previous Message | Pavel Stehule | 2013-03-21 07:00:16 | Re: Single-argument variant for array_length and friends? |