On Mon, May 9, 2011 at 3:53 PM, Greg Smith <greg@2ndquadrant.com> wrote:
> Richard, anything interesting in the server log after your crash?
Here is what the logs show:
2011-05-09 07:49:37 PDT LOG: server process (PID 2848) was terminated
by exception 0xC0000005
2011-05-09 07:49:37 PDT HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
2011-05-09 07:49:37 PDT LOG: terminating any other active server processes
2011-05-09 07:49:38 PDT WARNING: terminating connection because of
crash of another server process
2011-05-09 07:49:38 PDT 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.
2011-05-09 07:49:38 PDT HINT: In a moment you should be able to
reconnect to the database and repeat your command.
2011-05-09 07:49:38 PDT FATAL: the database system is in recovery mode
2011-05-09 07:49:38 PDT LOG: all server processes terminated; reinitializing
2011-05-09 07:49:48 PDT FATAL: pre-existing shared memory block is still in use
2011-05-09 07:49:48 PDT HINT: Check if there are any old server
processes still running, and terminate them.
--
Regards,
Richard Broersma Jr.
