Use pqsignal() in contrib programs rather than calling signal(2) directly.
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 17 Mar 2013 20:09:47 +0000 (16:09 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 17 Mar 2013 20:09:47 +0000 (16:09 -0400)
commit3c07fbf40bd0276e4be02fc72cba6b1cd62da301
treee536390c0b8ff52aad78d76fc8e540341f7a8149
parentb1fae823ee46a26e7e557591d659351835742537
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.
contrib/pg_standby/pg_standby.c
contrib/pg_test_fsync/pg_test_fsync.c