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 6631363

Browse filesBrowse files
committed
Fix whitespace.
Use tabs instead of spaces for new paragraph, like existing paragraphs.
1 parent 262454b commit 6631363
Copy full SHA for 6631363

File tree

Expand file treeCollapse file tree

1 file changed

+9
-9
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+9
-9
lines changed

‎src/port/pqsignal.c

Copy file name to clipboardExpand all lines: src/port/pqsignal.c
+9-9Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -30,15 +30,15 @@
3030
* this relies on pqsigaction() in src/backend/port/win32/signal.c, which
3131
* provides limited emulation of reliable signals.
3232
*
33-
* Frontend programs can use this version of pqsignal() to forward to the
34-
* native Windows signal() call if they wish, but beware that Windows signals
35-
* behave quite differently. Only the 6 signals required by C are supported.
36-
* SIGINT handlers run in another thread instead of interrupting an existing
37-
* thread, and the others don't interrupt system calls either, so SA_RESTART
38-
* is moot. All except SIGFPE have SA_RESETHAND semantics, meaning the
39-
* handler is reset to SIG_DFL each time it runs. The set of things you are
40-
* allowed to do in a handler is also much more restricted than on Unix,
41-
* according to the documentation.
33+
* Frontend programs can use this version of pqsignal() to forward to the
34+
* native Windows signal() call if they wish, but beware that Windows signals
35+
* behave quite differently. Only the 6 signals required by C are supported.
36+
* SIGINT handlers run in another thread instead of interrupting an existing
37+
* thread, and the others don't interrupt system calls either, so SA_RESTART
38+
* is moot. All except SIGFPE have SA_RESETHAND semantics, meaning the
39+
* handler is reset to SIG_DFL each time it runs. The set of things you are
40+
* allowed to do in a handler is also much more restricted than on Unix,
41+
* according to the documentation.
4242
*
4343
* ------------------------------------------------------------------------
4444
*/

0 commit comments

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