|
30 | 30 | * this relies on pqsigaction() in src/backend/port/win32/signal.c, which
|
31 | 31 | * provides limited emulation of reliable signals.
|
32 | 32 | *
|
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. |
42 | 42 | *
|
43 | 43 | * ------------------------------------------------------------------------
|
44 | 44 | */
|
|
0 commit comments