Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BBDB72E00C4 for ; Mon, 25 Feb 2008 11:58:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 32861-03-3 for ; Mon, 25 Feb 2008 11:58:09 -0400 (AST) X-Greylist: delayed 00:15:08.33263 by SQLgrey-1.7.5 Received: from outmail128160.authsmtp.net (outmail128160.authsmtp.net [62.13.128.160]) by postgresql.org (Postfix) with ESMTP id 57CFD2E004E for ; Mon, 25 Feb 2008 11:57:16 -0400 (AST) Received: from outmail128179.authsmtp.co.uk (outmail128179.authsmtp.co.uk [62.13.128.179]) by punt2.authsmtp.com (8.13.8/8.13.8/Kp) with ESMTP id m1PFfvPX038238; Mon, 25 Feb 2008 15:41:57 GMT Received: from [192.168.0.3] (85-211-31-42.dyn.gotadsl.co.uk [85.211.31.42]) (authenticated bits=0) by mail.authsmtp.com (8.13.8/8.13.8/Kp) with ESMTP id m1PFfuWK014757; Mon, 25 Feb 2008 15:41:57 GMT Subject: Re: System in Recovery Mode From: Simon Riggs To: Aaron Bono Cc: Postgres In-Reply-To: References: Content-Type: text/plain Date: Mon, 25 Feb 2008 15:42:53 +0000 Message-Id: <1203954173.4252.59.camel@ebony.site> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Server-Quench: 326cb776-e3b8-11dc-9670-001185d377ca X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksadBtFagBba1xT HGQLW1xEUVh7XWJ/ bg0fZQBDYEtPQQZr TkxLXVBXCwUmXB1h cEhbNWJydgFBfXk+ ZERgXj5YXkIpJ0F6 RFMBFj8OeGZhPDMC WUZfdx5UcAJLdhoR aVd4ByJDAzANdhER MyoSGQV5BiRENClQ CgALZWgfSkEVEyQt DzUFEThH X-Authentic-SMTP: 61633235383639.squirrel.dmpriest.net.uk:787/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system! X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/317 X-Sequence-Number: 28391 On Mon, 2008-02-25 at 08:11 -0600, Aaron Bono wrote: > Our database was going along just fine this morning when, out of the > blue, we started getting the following errors: > > FATAL: the database system is in recovery mode > > We are using PostgreSQL 8.1.3 on CentOS. I was the only person on the > machine and had recently started a small batch that had just finished > querying and updating the database. This batch runs constantly and > has not been changed in months. Your database has crashed and is recovering. You should look at the server log to find out when and why this happened, then either correct the problem or report the bug. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com