NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit8e861ea

committed

Explain postmaster's treatment of SIGURG.

Add a few words of comment to explain why SIGURG doesn't follow thedummy_handler pattern used for SIGUSR2, since that might otherwiseappear to be a bug.Discussion:https://postgr.es/m/4006115.1618577212%40sss.pgh.pa.us

1 parent4ed7f05 commit8e861eaCopy full SHA for 8e861ea

File tree

1 file changed

-0

lines changed

src/backend/postmaster
- postmaster.c

1 file changed

-0

lines changed

`‎src/backend/postmaster/postmaster.c`

Lines changed: 5 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -660,6 +660,11 @@ PostmasterMain(int argc, char *argv[])`
`660`	`660`	`pqsignal_pm(SIGCHLD,reaper);/* handle child termination */`
`661`	`661`
`662`	`662`	`#ifdefSIGURG`
	`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`	`+ */`
`663`	`668`	`pqsignal_pm(SIGURG,SIG_IGN);/* ignored */`
`664`	`669`	`#endif`
`665`	`670`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit8e861ea

File tree

1 file changed

1 file changed

`‎src/backend/postmaster/postmaster.c`

0 commit comments