Unresolved error 0xC0000409 on Windows Server
Matthew Gerber <gerber.matthew@gmail.com>
From: Matthew Gerber <gerber.matthew@gmail.com>
To: pgsql-hackers@postgresql.org
Date: 2012-11-02T18:25:33Z
Lists: pgsql-hackers
Hello, I am encountering an error on my Postgres installation for Windows Server 64-bit. The error was posted here<http://archives.postgresql.org/pgsql-bugs/2012-09/msg00014.php>a couple months ago; however, no solution was found on the pgsql-bugs list, so I am reposting it to pgsql-hackers in the hopes that someone will be able to help. My error message is identical to the one previously posted: 2012-11-01 22:36:26 EDT LOG: 00000: server process (PID 7060) was terminated by exception 0xC0000409 2012-11-01 22:36:26 EDT DETAIL: Failed process was running: INSERT INTO *[snipped SQL command]* 2012-11-01 22:36:26 EDT HINT: See C include file "ntstatus.h" for a description of the hexadecimal value. 2012-11-01 22:36:26 EDT LOCATION: LogChildExit, src\backend\postmaster\postmaster.c:2884 2012-11-01 22:36:26 EDT LOG: 00000: terminating any other active server processes 2012-11-01 22:36:26 EDT LOCATION: HandleChildCrash, src\backend\postmaster\postmaster.c:2682 2012-11-01 22:36:26 EDT WARNING: 57P00: terminating connection because of crash of another server process 2012-11-01 22:36:26 EDT DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2012-11-01 22:36:26 EDT HINT: In a moment you should be able to reconnect to the database and repeat your command. 2012-11-01 22:36:26 EDT LOCATION: quickdie, src\backend\tcop\postgres.c:2556 2012-11-01 22:36:26 EDT LOG: 00000: all server processes terminated; reinitializing 2012-11-01 22:36:26 EDT LOCATION: PostmasterStateMachine, src\backend\postmaster\postmaster.c:3135 2012-11-01 22:36:36 EDT FATAL: XX000: pre-existing shared memory block is still in use 2012-11-01 22:36:36 EDT HINT: Check if there are any old server processes still running, and terminate them. 2012-11-01 22:36:36 EDT LOCATION: PGSharedMemoryCreate, src\backend\port\win32_shmem.c:194 The error happens regularly while performing database INSERTS. The [snipped SQL command] part above contains the INSERT command that was executing when the server crashed. After restarting the server the command executes fine, so it's not a problem with the command. I installed Postgres from the standard Windows binary "postgresql-9.2.1-1-windows-x64.exe" and I have not changed any configuration settings from their default values. Does anyone know what might be happening and how I might fix it? Thanks, Matt