aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThomas Munro <tmunro@postgresql.org>2021-04-19 10:22:31 +1200
committerThomas Munro <tmunro@postgresql.org>2021-04-19 10:35:51 +1200
commit8e861eaae86eeaf5589963c9b1c7ce6d4c2acbb5 (patch)
treed99db2c9f52a19cef128894686763ebf49a0347d
parent4ed7f0599a8984d9ed967780a157d9b23d03fbb5 (diff)
downloadpostgresql-8e861eaae86eeaf5589963c9b1c7ce6d4c2acbb5.tar.gz
postgresql-8e861eaae86eeaf5589963c9b1c7ce6d4c2acbb5.zip
Explain postmaster's treatment of SIGURG.
Add a few words of comment to explain why SIGURG doesn't follow the dummy_handler pattern used for SIGUSR2, since that might otherwise appear to be a bug. Discussion: https://postgr.es/m/4006115.1618577212%40sss.pgh.pa.us
-rw-r--r--src/backend/postmaster/postmaster.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
index 4a3ca78c1b7..b05db5a4735 100644
--- a/src/backend/postmaster/postmaster.c
+++ b/src/backend/postmaster/postmaster.c
@@ -660,6 +660,11 @@ PostmasterMain(int argc, char *argv[])
pqsignal_pm(SIGCHLD, reaper); /* handle child termination */
#ifdef SIGURG
+ /*
+ * Ignore SIGURG for now. Child processes may change this (see
+ * InitializeLatchSupport), but they will not receive any such signals
+ * until they wait on a latch.
+ */
pqsignal_pm(SIGURG, SIG_IGN); /* ignored */
#endif