pgsql: Remove bgw_sighup and bgw_sigterm. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Remove bgw_sighup and bgw_sigterm.
Date
Msg-id E1V1LaL-0000fc-89@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Remove bgw_sighup and bgw_sigterm.

Per discussion on pgsql-hackers, these aren't really needed.  Interim
versions of the background worker patch had the worker starting with
signals already unblocked, which would have made this necessary.
But the final version does not, so we don't really need it; and it
doesn't work well with the new facility for starting dynamic background
workers, so just rip it out.

Also per discussion on pgsql-hackers, back-patch this change to 9.3.
It's best to get the API break out of the way before we do an
official release of this facility, to avoid more pain for extension
authors later.

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/295f9bbf1d2d1e985471bd523c7c9bfd3d134759

Modified Files
--------------
contrib/worker_spi/worker_spi.c     |    6 ++++--
doc/src/sgml/bgworker.sgml          |   13 +------------
src/backend/postmaster/postmaster.c |   12 ++----------
src/include/postmaster/bgworker.h   |    3 ---
4 files changed, 7 insertions(+), 27 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Adjust HeapTupleSatisfies* routines to take a HeapTuple.
Next
From: Robert Haas
Date:
Subject: pgsql: Remove bgw_sighup and bgw_sigterm.