Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit1e31484

Browse files
committed
Mark two signal flags as sig_atomic_t in pgbench and pg_test_fsync
Two booleans used for timeout tracking were used within some SIGALRMsignal handlers, but they were not declared as sig_atomic_t, so markthem as such. This has no consequence on WIN32 for both tools.Author: Ranier VilelaReviewed-by: Michael Paquier, Masahiko SawadaDiscussion:https://postgr.es/m/CAEudQArCDQQiPiFR16=yu9k5s2tp4tgEe1U1ZbkW4ofx81AWWQ@mail.gmail.com
1 parent02ac05b commit1e31484

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

‎src/bin/pg_test_fsync/pg_test_fsync.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ static char full_buf[DEFAULT_XLOG_SEG_SIZE],
6868
*filename=FSYNC_FILENAME;
6969
staticstructtimevalstart_t,
7070
stop_t;
71-
staticboolalarm_triggered= false;
71+
staticsig_atomic_talarm_triggered= false;
7272

7373

7474
staticvoidhandle_args(intargc,char*argv[]);

‎src/bin/pgbench/pgbench.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -310,7 +310,7 @@ const char *progname;
310310

311311
#defineWSEP '@'/* weight separator */
312312

313-
volatilebooltimer_exceeded= false;/* flag from signal handler */
313+
volatilesig_atomic_ttimer_exceeded= false;/* flag from signal handler */
314314

315315
/*
316316
* We don't want to allocate variables one by one; for efficiency, add a

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp