|
8 | 8 | * |
9 | 9 | * |
10 | 10 | * IDENTIFICATION |
11 | | - * $Header: /cvsroot/pgsql/src/backend/libpq/pqsignal.c,v 1.3 1996/11/06 08:48:32 scrappy Exp $ |
| 11 | + * $Header: /cvsroot/pgsql/src/backend/libpq/pqsignal.c,v 1.4 1996/11/18 02:25:09 bryanh Exp $ |
12 | 12 | * |
13 | 13 | * NOTES |
14 | 14 | *This shouldn't be in libpq, but the monitor and some other |
15 | 15 | *things need it... |
16 | 16 | * |
17 | | - *------------------------------------------------------------------------- |
18 | | - */ |
| 17 | + * A NOTE ABOUT SIGNAL HANDLING ACROSS THE VARIOUS PLATFORMS. |
| 18 | + * |
| 19 | + * config.h defines the macro USE_POSIX_SIGNALS for some platforms and |
| 20 | + * not for others. This file and pqsignal.h use that macro to decide |
| 21 | + * how to handle signalling. |
| 22 | + * |
| 23 | + * signal(2) handling - this is here because it affects some of |
| 24 | + * the frontend commands as well as the backend server. |
| 25 | + * |
| 26 | + * Ultrix and SunOS provide BSD signal(2) semantics by default. |
| 27 | + * |
| 28 | + * SVID2 and POSIX signal(2) semantics differ from BSD signal(2) |
| 29 | + * semantics. We can use the POSIX sigaction(2) on systems that |
| 30 | + * allow us to request restartable signals (SA_RESTART). |
| 31 | + * |
| 32 | + * Some systems don't allow restartable signals at all unless we |
| 33 | + * link to a special BSD library. |
| 34 | + * |
| 35 | + * We devoutly hope that there aren't any systems that provide |
| 36 | + * neither POSIX signals nor BSD signals. The alternative |
| 37 | + * is to do signal-handler reinstallation, which doesn't work well |
| 38 | + * at all. |
| 39 | + * ------------------------------------------------------------------------*/ |
19 | 40 | #include<postgres.h> |
20 | 41 |
|
21 | 42 | #include<libpq/pqsignal.h> |
|
