aboutsummaryrefslogtreecommitdiff
path: root/src/bin/psql/common.c
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2004-11-01 19:21:50 +0000
committerBruce Momjian <bruce@momjian.us>2004-11-01 19:21:50 +0000
commit7fad5fff0df0476ca80716153963d90c5776acf3 (patch)
treea03f03925ff155854140f7c8c049bb682d8ff837 /src/bin/psql/common.c
parent9c3d654a16b7f8299ea4a299c8c581ffd973fea1 (diff)
downloadpostgresql-7fad5fff0df0476ca80716153963d90c5776acf3.tar.gz
postgresql-7fad5fff0df0476ca80716153963d90c5776acf3.zip
That's just the lovely way windows handles a "segfault". Gotta be really
interesting for MS to catch all those dumps... Anyway. Oops. Seems I ran my regression tests with the old psql, and just managed to update the backend, when I tested that patch. Turns out there are codepaths where we'd access the Critical Section before it was initialized. Attached patch breaks the initializeation off to a separate part and adds that one to a much earlier position in the program. Magnus Hagander
Diffstat (limited to 'src/bin/psql/common.c')
-rw-r--r--src/bin/psql/common.c9
1 files changed, 7 insertions, 2 deletions
diff --git a/src/bin/psql/common.c b/src/bin/psql/common.c
index 0089d5d2c81..44278aa9265 100644
--- a/src/bin/psql/common.c
+++ b/src/bin/psql/common.c
@@ -3,7 +3,7 @@
*
* Copyright (c) 2000-2004, PostgreSQL Global Development Group
*
- * $PostgreSQL: pgsql/src/bin/psql/common.c,v 1.93 2004/10/30 23:10:50 tgl Exp $
+ * $PostgreSQL: pgsql/src/bin/psql/common.c,v 1.94 2004/11/01 19:21:50 momjian Exp $
*/
#include "postgres_fe.h"
#include "common.h"
@@ -307,9 +307,14 @@ consoleHandler(DWORD dwCtrlType)
}
void
-setup_cancel_handler(void)
+setup_win32_locks(void)
{
InitializeCriticalSection(&cancelConnLock);
+}
+
+void
+setup_cancel_handler(void)
+{
SetConsoleCtrlHandler(consoleHandler, TRUE);
}