Commit b7af62e4 authored by Bruce Momjian's avatar Bruce Momjian

Avoid longjump/vfork warning about line_saved_in_history variable by

making it volatile.
parent a073a704
...@@ -3,7 +3,7 @@ ...@@ -3,7 +3,7 @@
* *
* Copyright (c) 2000-2006, PostgreSQL Global Development Group * Copyright (c) 2000-2006, PostgreSQL Global Development Group
* *
* $PostgreSQL: pgsql/src/bin/psql/mainloop.c,v 1.76 2006/06/05 03:55:00 momjian Exp $ * $PostgreSQL: pgsql/src/bin/psql/mainloop.c,v 1.77 2006/06/05 14:47:38 momjian Exp $
*/ */
#include "postgres_fe.h" #include "postgres_fe.h"
#include "mainloop.h" #include "mainloop.h"
...@@ -41,8 +41,8 @@ MainLoop(FILE *source) ...@@ -41,8 +41,8 @@ MainLoop(FILE *source)
char *line; /* current line of input */ char *line; /* current line of input */
int added_nl_pos; int added_nl_pos;
bool success; bool success;
bool line_saved_in_history;
volatile bool line_saved_in_history;
volatile int successResult = EXIT_SUCCESS; volatile int successResult = EXIT_SUCCESS;
volatile backslashResult slashCmdStatus = PSQL_CMD_UNKNOWN; volatile backslashResult slashCmdStatus = PSQL_CMD_UNKNOWN;
volatile promptStatus_t prompt_status = PROMPT_READY; volatile promptStatus_t prompt_status = PROMPT_READY;
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment