Re: PGSQL service dieing... - Mailing list pgsql-general

From Richard Huxton
Subject Re: PGSQL service dieing...
Date
Msg-id 40D6B876.6020406@archonet.com
Whole thread Raw
In response to PGSQL service dieing...  ("Daniel Baughman" <danrb@codenet.net>)
List pgsql-general
Daniel Baughman wrote:
>
> Warning: terminatin connection because of crash of another server process
> Detail: The postmaster has commanded this server process to roll back the
> current transaction and exit, because nother server process exited
> abnormally and possible corrupted shared memory
> Hint: ina moment you should be able to reconnect to the database and repeat
> your command

There should be something to say what killed "another server process".

> Could a series of commands, say perhaps a few hundred of the course of an
> hour, that had incorrect syntax cause a problem like this?  Is there
> anywhere I can go for more info?

No - backends should only die in the event of hardware problems/out of
memory/disk or they've been killed by an administrator.

The first thing you'll need to do is find out why the initial problem
occurs. There should be something in the logs to say what is happening.

--
   Richard Huxton
   Archonet Ltd

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Limit connections per user
Next
From: Madison Kelly
Date:
Subject: New to the list; would this be an okay question?