Hi there, one of our systems on a PG 8.2 database crashes nearly daily; others are running fine. Host OS of this system is Windows, if the db crashes nothing is written in the OS event logs. The database log show every time the following messages: 2009-09-23 10:21:30 LOG: server process (PID 1240) exited with exit code -1073741819 2009-09-23 10:21:30 LOG: terminating any other active server processes 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:30 WARNING: terminating connection because of crash of another server process 2009-09-23 10:21:30 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. 2009-09-23 10:21:30 HINT: In a moment you should be able to reconnect to the database and repeat your command. 2009-09-23 10:21:32 LOG: all server processes terminated; reinitializing The exit code in the first log line is the same on every crash even. But I could not find anything about it on the net. Other applications on the same system doesn´t show notes that reference to hardware based causes. May anyone give me a hint what´s wrong with this system or what we can do to avoid further crashes? Regards Michael -- Diese Mail wurde auf Viren geprüft mit Hilfe von Astaro Mail Gateway. http://www.astaro.com -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
