1berry/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Mark two signal flags as sig_atomic_t in pgbench and pg_test_fsync

Browse Source 
Two booleans used for timeout tracking were used within some SIGALRM
signal handlers, but they were not declared as sig_atomic_t, so mark
them as such.  This has no consequence on WIN32 for both tools.

Author: Ranier Vilela
Reviewed-by: Michael Paquier, Masahiko Sawada
Discussion: https://postgr.es/m/CAEudQArCDQQiPiFR16=yu9k5s2tp4tgEe1U1ZbkW4ofx81AWWQ@mail.gmail.com
This commit is contained in:
Michael Paquier 2022-11-26 20:12:33 +09:00
parent 02ac05b4c0
commit 1e314847dd
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/bin/pg_test_fsync/pg_test_fsync.c
View File

@ -68,7 +68,7 @@ static char full_buf[DEFAULT_XLOG_SEG_SIZE],
*filename = FSYNC_FILENAME; *filename = FSYNC_FILENAME;
static struct timeval start_t, static struct timeval start_t,
stop_t; stop_t;
static bool alarm_triggered = false; static sig_atomic_t alarm_triggered = false;
static void handle_args(int argc, char *argv[]); static void handle_args(int argc, char *argv[]);

2
src/bin/pgbench/pgbench.c
View File

@ -310,7 +310,7 @@ const char *progname;
#define WSEP '@' /* weight separator */ #define WSEP '@' /* weight separator */
volatile bool timer_exceeded = false; /* flag from signal handler */ volatile sig_atomic_t timer_exceeded = false; /* flag from signal handler */
/* /*
* We don't want to allocate variables one by one; for efficiency, add a * We don't want to allocate variables one by one; for efficiency, add a