Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 6052E1337B6D for ; Thu, 18 Nov 2010 14:04:23 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 46871-08 for ; Thu, 18 Nov 2010 18:04:15 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 9BD8A1337B58 for ; Thu, 18 Nov 2010 14:04:15 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id oAII4DbO004068; Thu, 18 Nov 2010 13:04:14 -0500 (EST) To: Wells Oliver cc: pgsql-admin@postgresql.org Subject: Re: 8.4 process killed- what sort of recovery options do I have? In-reply-to: <6BDF410DD500E841A60A6D183F26E26E096BB9D2@svrmailbe2.padres.com> References: <6BDF410DD500E841A60A6D183F26E26E096BB9D2@svrmailbe2.padres.com> Comments: In-reply-to Wells Oliver message dated "Thu, 18 Nov 2010 09:42:49 -0800" Date: Thu, 18 Nov 2010 13:04:13 -0500 Message-ID: <4067.1290103453@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201011/151 X-Sequence-Number: 36117 Wells Oliver writes: > For whatever reason- investigations still pending- the postgres process > froze up and I had to do a killall b/c pg_ctlcluster would not revive > the thing. Everything seems to be in working order, but I'd like to know > if there's any kind of consistency check I should run in light of > events. Also, what's the best way to track down the reason for the > crash? Just get into /var/log/postgresql and poke around? I don't think you need to worry about your data. Crash recovery is a well-tested aspect of Postgres ;-). As for figuring out what happened, did you force core dumps? Stack traces from the dumps would be most useful. regards, tom lane