8000 Avoid longjump/vfork warning about line_saved_in_history variable by · postgrespro/postgres_cluster@b7af62e · GitHub
[go: up one dir, main page]
Skip to content

Commit b7af62e

Browse files
bmomjianbmomjian
committed
Avoid longjump/vfork warning about line_saved_in_history variable by
making it volatile.
1 parent a073a70 commit b7af62e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

‎src/bin/psql/mainloop.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
*
44
* Copyright (c) 2000-2006, PostgreSQL Global Development Group
55
*
6-
* $PostgreSQL: pgsql/src/bin/psql/mainloop.c,v 1.76 2006/06/05 03:55:00 momjian Exp $
6+
* $PostgreSQL: pgsql/src/bin/psql/mainloop.c,v 1.77 2006/06/05 14:47:38 momjian Exp $
77
*/
88
#include "postgres_fe.h"
99
#include "mainloop.h"
@@ -41,8 +41,8 @@ MainLoop(FILE *source)
4141
char *line; /* current line of input */
4242
int added_nl_pos;
4343
bool success;
44-
bool line_saved_in_history;
45-
44+
45+
volatile bool line_saved_in_history;
4646
volatile int successResult = EXIT_SUCCESS;
4747
volatile backslashResult slashCmdStatus = PSQL_CMD_UNKNOWN;
4848
volatile promptStatus_t prompt_status = PROMPT_READY;

0 commit comments

Comments
 (0)
0