Re: FATAL: the database system is in recovery mode - Mailing list pgsql-general

From Doug McNaught
Subject Re: FATAL: the database system is in recovery mode
Date
Msg-id 87r7rnqykv.fsf@asmodeus.mcnaught.org
Whole thread Raw
In response to Re: FATAL: the database system is in recovery mode  (Ron St-Pierre <rstpierre@syscor.com>)
List pgsql-general
Ron St-Pierre <rstpierre@syscor.com> writes:

> Jul  7 09:32:58 imp postgres[26784]: [448-1] LOG:  server process (PID
> 32349) was terminated by signal 11

This is the critical event--one of the backends got a segfault.  This
often means bad hardware--either your RAM is faulty, or something got
corrupted on disk and caused a bad pointer reference.  Or maybe an
overheating CPU, if a fan failed.

That said, it's also possible that it's a Postgres bug, but it's more
likely to be hardware...

> Anyway my original question still stands, any idea how to avoid this
> problem in the future?

Test your hardware and replace any bad components.

-Doug

pgsql-general by date:

Previous
From: Ron St-Pierre
Date:
Subject: Re: FATAL: the database system is in recovery mode
Next
From: MargaretGillon@chromalloy.com
Date:
Subject: PGADMIN default storage EXTENDED for Character fields