X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 22F47D6D04 for ; Tue, 15 Nov 2005 00:18:49 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 53679-03 for ; Tue, 15 Nov 2005 04:18:09 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 71B9CD6D8C for ; Tue, 15 Nov 2005 00:18:08 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jAF4HwrF006228; Mon, 14 Nov 2005 23:17:58 -0500 (EST) To: Christopher Kings-Lynne cc: Tim Allen , Hackers , pgsql-admin@postgresql.org Subject: Re: [HACKERS] Major Problem, need help! Can't run our website! In-reply-to: <43795E7D.7090706@familyhealth.com.au> References: <227C7FFACEA9D9118BD600096BA5A7CA011E188B@EIBPOST> <43795A96.9070500@proximity.com.au> <43795E7D.7090706@familyhealth.com.au> Comments: In-reply-to Christopher Kings-Lynne message dated "Tue, 15 Nov 2005 12:05:17 +0800" Date: Mon, 14 Nov 2005 23:17:58 -0500 Message-ID: <6227.1132028278@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[MANY_EXCLAMATIONS=0] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/170 X-Sequence-Number: 19543 Christopher Kings-Lynne writes: > Would it be wise or insane for us to to mention in the startup error a > HINT that if you've removed such files, only hope is full restore from > backup or pg_resetxlog with data loss? Not sure that we should have a HINT recommending a worst-case-scenario course of action as the first resort. We'll have people blowing away their data for what might be relatively fixable problems (eg, bogus permissions on the pg_xlog directory, which I think was an issue that just came up a day or two ago ...) (We're all really jumping to conclusions here anyway. The guy may have been foolish to remove xlog files, but that doesn't explain why his postmaster isn't running. There's some facts missing in that report.) regards, tom lane