| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Euler Taveira <euler(at)timbira(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SIGHUP not received by custom bgworkers if postmaster is notified |
| Date: | 2013-04-11 00:55:51 |
| Message-ID: | CAB7nPqRSKi0SqAbD0VQOfqXzQfSMZnjCwoGOuDkEGT7brGFt5g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thanks for committing the fix!
On Thu, Apr 11, 2013 at 4:11 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>wrote:
> Michael Paquier escribió:
> > Hi all,
> >
> > Please find attached a simple example of bgworker that logs a message
> each
> > time a SIGTERM or SIGHUP signal is received by it:
> > - "hello signal: processed SIGHUP" when SIGHUP is handled by my example
> > - "hello signal: processed SIGTERM" when SIGTERM is handled by my example
>
> I committed some improvements to worker_spi this morning that I think
> enough demostrate signal handling capabilities, which I think is what
> your submitted code would do. If you see more use for a separate body
> of sample worker code, by all means do submit that.
>
Sure.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2013-04-11 01:57:06 | synchronize_seqscans' description is a bit misleading |
| Previous Message | Alvaro Herrera | 2013-04-10 23:49:50 | Re: [sepgsql 3/3] Add db_procedure:execute permission checks |