Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 8e861ea

Browse filesBrowse files
committed
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
1 parent 4ed7f05 commit 8e861ea
Copy full SHA for 8e861ea

File tree

Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+5
-0
lines changed

‎src/backend/postmaster/postmaster.c

Copy file name to clipboardExpand all lines: src/backend/postmaster/postmaster.c
+5Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -660,6 +660,11 @@ PostmasterMain(int argc, char *argv[])
660660
pqsignal_pm(SIGCHLD, reaper); /* handle child termination */
661661

662662
#ifdef SIGURG
663+
/*
664+
* Ignore SIGURG for now. Child processes may change this (see
665+
* InitializeLatchSupport), but they will not receive any such signals
666+
* until they wait on a latch.
667+
*/
663668
pqsignal_pm(SIGURG, SIG_IGN); /* ignored */
664669
#endif
665670

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.