| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Chapman Flack <chap(at)anastigmatix(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Signals in a BGW |
| Date: | 2017-12-05 01:11:18 |
| Message-ID: | CAB7nPqQv6_9s97skJ_cn6m9mSNZu19azQgEc0iB0xCS1X13-QA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 5, 2017 at 10:03 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:
> pglogical sets up its own handler 'handle_sigterm'. However, it now does
> much the same as src/backend/tcop/postgres.c's 'die' function, just without
> the single-user mode checks.
Documentation shows a simple example of that:
https://www.postgresql.org/docs/devel/static/source-conventions.html
> IMO it's silly to customise them, and a bad example.
I don't agree. It is not silly to have background workers being able
to take clean up actions and have their own tracking with some
sig_atomic_t flags.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-12-05 01:15:19 | Re: es_query_dsa is broken |
| Previous Message | Craig Ringer | 2017-12-05 01:03:48 | Re: Signals in a BGW |