pgsql: Mark two signal flags as sig_atomic_t in pgbench and pg_test_fsy - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: Mark two signal flags as sig_atomic_t in pgbench and pg_test_fsy
Date
Msg-id E1oyt9h-000t9y-Q7@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Mark two signal flags as sig_atomic_t in pgbench and pg_test_fsync

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

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1e314847dd69c6b3b85d36e5873d80b9e4cf028a

Modified Files
--------------
src/bin/pg_test_fsync/pg_test_fsync.c | 2 +-
src/bin/pgbench/pgbench.c             | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgsql: Prevent port collisions between concurrent TAP tests
Next
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Prevent port collisions between concurrent TAP tests