diff options
author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-04-10 15:59:45 -0300 |
---|---|---|
committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-04-10 15:59:45 -0300 |
commit | 61a7d576f2a287ef59071da9d9d7a0cd473ed98b (patch) | |
tree | 8f6727987d71605b6989352b7cdcd5f50e41fc8c | |
parent | 6f5b8beb64d481c28a483090d10099c8d619c797 (diff) | |
download | postgresql-61a7d576f2a287ef59071da9d9d7a0cd473ed98b.tar.gz postgresql-61a7d576f2a287ef59071da9d9d7a0cd473ed98b.zip |
Fix SIGHUP handling by unconnected bgworkers
Add a SignalUnconnectedWorkers() call so that non-database-connected background
workers are also notified when postmaster is SIGHUPped. Previously, only
database-connected workers were.
Michael Paquier (bug report and fix)
-rw-r--r-- | src/backend/postmaster/postmaster.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c index 298ad5e1ec4..5ff35774787 100644 --- a/src/backend/postmaster/postmaster.c +++ b/src/backend/postmaster/postmaster.c @@ -2280,6 +2280,7 @@ SIGHUP_handler(SIGNAL_ARGS) (errmsg("received SIGHUP, reloading configuration files"))); ProcessConfigFile(PGC_SIGHUP); SignalChildren(SIGHUP); + SignalUnconnectedWorkers(SIGHUP); if (StartupPID != 0) signal_child(StartupPID, SIGHUP); if (BgWriterPID != 0) |