Unresolved error 0xC0000409 on Windows Server - Mailing list pgsql-hackers

From Matthew Gerber
Subject Unresolved error 0xC0000409 on Windows Server
Date
Msg-id CAOcpbfqPLwLq_0BBT4srkbUZZ5kp52_qeeAeqE0UiTh58045_Q@mail.gmail.com
Whole thread Raw
Responses Re: Unresolved error 0xC0000409 on Windows Server  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Hello,<br /><br />I am encountering an error on my Postgres installation for Windows Server 64-bit. The error was
posted<a href="http://archives.postgresql.org/pgsql-bugs/2012-09/msg00014.php">here</a> a couple months ago; however,
nosolution was found on the pgsql-bugs list, so I am reposting it to pgsql-hackers in the hopes that someone will be
ableto help. My error message is identical to the one previously posted:<br /><br />2012-11-01 22:36:26 EDT LOG: 
00000:server process (PID 7060) was terminated by exception 0xC0000409<br />2012-11-01 22:36:26 EDT DETAIL:  Failed
processwas running: INSERT INTO <b>[snipped SQL command]</b><br />2012-11-01 22:36:26 EDT HINT:  See C include file
"ntstatus.h"for a description of the hexadecimal value.<br /> 2012-11-01 22:36:26 EDT LOCATION:  LogChildExit,
src\backend\postmaster\postmaster.c:2884<br/>2012-11-01 22:36:26 EDT LOG:  00000: terminating any other active server
processes<br/>2012-11-01 22:36:26 EDT LOCATION:  HandleChildCrash, src\backend\postmaster\postmaster.c:2682<br />
2012-11-0122:36:26 EDT WARNING:  57P00: terminating connection because of crash of another server process<br
/>2012-11-0122:36:26 EDT DETAIL:  The postmaster has commanded this server process to roll back the current transaction
andexit, because another server process exited abnormally and possibly corrupted shared memory.<br /> 2012-11-01
22:36:26EDT HINT:  In a moment you should be able to reconnect to the database and repeat your command.<br />2012-11-01
22:36:26EDT LOCATION:  quickdie, src\backend\tcop\postgres.c:2556<br />2012-11-01 22:36:26 EDT LOG:  00000: all server
processesterminated; reinitializing<br /> 2012-11-01 22:36:26 EDT LOCATION:  PostmasterStateMachine,
src\backend\postmaster\postmaster.c:3135<br/>2012-11-01 22:36:36 EDT FATAL:  XX000: pre-existing shared memory block is
stillin use<br />2012-11-01 22:36:36 EDT HINT:  Check if there are any old server processes still running, and
terminatethem.<br /> 2012-11-01 22:36:36 EDT LOCATION:  PGSharedMemoryCreate, src\backend\port\win32_shmem.c:194<br
/><br/>The error happens regularly while performing database INSERTS. The [snipped SQL command] part above contains the
INSERTcommand that was executing when the server crashed. After restarting the server the command executes fine, so
it'snot 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.<br
/><br/>Does anyone know what might be happening and how I might fix it?<br /><br />Thanks,<br />Matt<br /> 

pgsql-hackers by date:

Previous
From: Shaun Thomas
Date:
Subject: Re: Synchronous commit not... synchronous?
Next
From: Merlin Moncure
Date:
Subject: Re: Unresolved error 0xC0000409 on Windows Server