Re: psql: FATAL: the database system is in recovery mode

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Bhushan Verma <verma(dot)bhushan(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: psql: FATAL: the database system is in recovery mode
Date: 2009-06-24 23:38:05
Message-ID: 4A42B8DD.4050202@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-novice

Bhushan Verma wrote:

>>> Is it a particular one, or does it crash at random?
>
> its crash at random.

Random segfaults easily by application bugs ( memory corruption,
accessing uninitialized memory and dereferencing pointers there, etc )
or hardware issues like bad CPU/CPU cache/memory, overheating, etc.

Are you having issues with any other applications?

If you can afford the load, consider running something quite CPU/memory
intensive for a while - say, a big compile job - and make sure it all
goes smoothly.

It'd also be interesting to know whether a separate PostgreSQL instance
with a fresh database had issues, but that's probably not practical for
you to test.

Most likely it's some kind of corrupt database triggering a subtle bug
somewhere in Pg, anyway...

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message pamelant 2009-06-25 09:28:50 BUG #4878: function age() give a wrong interval
Previous Message Scott Mead 2009-06-24 22:45:58 Re: [BUGS] Integrity check

Browse pgsql-novice by date

  From Date Subject
Next Message Tim Ryan 2009-06-25 13:36:44 Re: Problems importing csv files
Previous Message Bhushan Verma 2009-06-24 13:22:11 Re: psql: FATAL: the database system is in recovery mode