database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00
Code Activity

Explain postmaster's treatment of SIGURG.

Browse Source 
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
This commit is contained in:
Thomas Munro
2021-04-19 10:22:31 +12:00
parent 4ed7f0599a
commit 8e861eaae8
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/backend/postmaster/postmaster.c
View File

@ -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