BUG #5260: Postgre crashed unexpectedly

From: "Toni Helenius" <toni(dot)helenius(at)syncrontech(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5260: Postgre crashed unexpectedly
Date: 2010-01-04 10:29:22
Message-ID: 201001041029.o04ATMYC020922@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5260
Logged by: Toni Helenius
Email address: toni(dot)helenius(at)syncrontech(dot)com
PostgreSQL version: 8.3.9
Operating system: Windows 2008 Server Enterprise
Description: Postgre crashed unexpectedly
Details:

Postgre database was running normally and several applications using it
normally like any other day. Then the Postge just died and didn't recover by
itself.. Here is the log:

2009-12-31 13:41:09 EET LOG: server process (PID 7020) was terminated by
exception 0xC0000005
2009-12-31 13:41:09 EET HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
2009-12-31 13:41:09 EET LOG: terminating any other active server processes
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET WARNING: terminating connection because of crash of
another server process
2009-12-31 13:41:09 EET 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-12-31 13:41:09 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2009-12-31 13:41:09 EET LOG: loaded library
"$libdir/plugins/plugin_debugger.dll"
2009-12-31 13:41:09 EET FATAL: the database system is in recovery mode
2009-12-31 13:41:10 EET LOG: all server processes terminated;
reinitializing
2009-12-31 13:41:20 EET FATAL: pre-existing shared memory block is still in
use
2009-12-31 13:41:20 EET HINT: Check if there are any old server processes
still running, and terminate them.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2010-01-04 10:36:27 Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints
Previous Message Jasen Betts 2010-01-04 10:06:48 Re: BUG #5258: Unique and foreign key constraints fail on columns with reserved names, but not check constraints