diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-03-17 16:09:47 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-03-17 16:09:47 -0400 |
| commit | 3c07fbf40bd0276e4be02fc72cba6b1cd62da301 (patch) | |
| tree | e536390c0b8ff52aad78d76fc8e540341f7a8149 /src/backend/access/gist/gistvacuum.c | |
| parent | b1fae823ee46a26e7e557591d659351835742537 (diff) | |
| download | postgresql-3c07fbf40bd0276e4be02fc72cba6b1cd62da301.tar.gz | |
Use pqsignal() in contrib programs rather than calling signal(2) directly.
The semantics of signal(2) are more variable than one could wish; in
particular, on strict-POSIX platforms the signal handler will be reset
to SIG_DFL when the signal is delivered. This demonstrably breaks
pg_test_fsync's use of SIGALRM. The other changes I made are not
absolutely necessary today, because the called handlers all exit the
program anyway. But it seems like a good general practice to use
pqsignal() exclusively in Postgres code, now that we have it available
everywhere.
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions