postgres.git / summary / log / commit / refs

commit    52e98d45023027de0fa8e4eee2d53e2c20185812
Author:   Peter Eisentraut <peter@eisentraut.org>
Date:     Wed Dec 06 09:11:36 2023 +0000
First released in: 17.0

    Use signal-safe functions in signal handler
    
    According to signal-safety(7), exit(3) and puts(3) are not safe to call
    in a signal handler.
    
    Author: Tristan Partin <tristan@neon.tech>
    Discussion: https://www.postgresql.org/message-id/flat/CTVDKVZCCVSY.1XQ87UL50KQRD%40gonk


src/bin/pg_test_fsync/pg_test_fsync.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/bin/pg_test_fsync/pg_test_fsync.c b/src/bin/pg_test_fsync/pg_test_fsync.c index f56e494f70f..f109aa57174 100644 --- a/src/bin/pg_test_fsync/pg_test_fsync.c +++ b/src/bin/pg_test_fsync/pg_test_fsync.c @@ -602,8 +602,8 @@ signal_cleanup(SIGNAL_ARGS) if (needs_unlink) unlink(filename); /* Finish incomplete line on stdout */ - puts(""); - exit(1); + write(STDOUT_FILENO, "\n", 1); + _exit(1); } #ifdef HAVE_FSYNC_WRITETHROUGH [parent: 7636725b922c]