summaryrefslogtreecommitdiff
path: root/src/bin/psql/startup.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/startup.c
parent9c3d654a16b7f8299ea4a299c8c581ffd973fea1 (diff)
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/startup.c')
-rw-r--r--src/bin/psql/startup.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/bin/psql/startup.c b/src/bin/psql/startup.c
index 87f9200d7cd..d7ef12a315a 100644
--- a/src/bin/psql/startup.c
+++ b/src/bin/psql/startup.c
@@ -3,7 +3,7 @@
*
* Copyright (c) 2000-2004, PostgreSQL Global Development Group
*
- * $PostgreSQL: pgsql/src/bin/psql/startup.c,v 1.104 2004/10/16 03:10:16 momjian Exp $
+ * $PostgreSQL: pgsql/src/bin/psql/startup.c,v 1.105 2004/11/01 19:21:50 momjian Exp $
*/
#include "postgres_fe.h"
@@ -121,6 +121,7 @@ main(int argc, char *argv[])
#ifdef WIN32
setvbuf(stderr, NULL, _IONBF, 0);
+ setup_win32_locks();
#endif
pset.cur_cmd_source = stdin;
pset.cur_cmd_interactive = false;