| From: | Doug McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | Ron St-Pierre <rstpierre(at)syscor(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: FATAL: the database system is in recovery mode |
| Date: | 2004-07-07 21:47:28 |
| Message-ID: | 87r7rnqykv.fsf@asmodeus.mcnaught.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ron St-Pierre <rstpierre(at)syscor(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MargaretGillon | 2004-07-07 22:18:23 | PGADMIN default storage EXTENDED for Character fields |
| Previous Message | Ron St-Pierre | 2004-07-07 21:42:26 | Re: FATAL: the database system is in recovery mode |