X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id DD02C9FB235 for ; Fri, 28 Jul 2006 00:40:08 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 94275-05 for ; Fri, 28 Jul 2006 00:39:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 6E07F9FB220 for ; Fri, 28 Jul 2006 00:39:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k6S3dls3015901; Thu, 27 Jul 2006 23:39:47 -0400 (EDT) To: "Mark Liberman" cc: pgsql-admin@postgresql.org Subject: Re: Corrupted DB - Help In-reply-to: <9D938282F8C6EE43B748B910386DE93E0138B4BE@srvgpimail1.GPI.local> References: <9D938282F8C6EE43B748B910386DE93E0138B4BE@srvgpimail1.GPI.local> Comments: In-reply-to "Mark Liberman" message dated "Thu, 27 Jul 2006 18:55:28 -0700" Date: Thu, 27 Jul 2006 23:39:47 -0400 Message-ID: <15900.1154057987@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.037 tagged_above=0 required=5 tests=AWL, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200607/251 X-Sequence-Number: 22497 "Mark Liberman" writes: > <4983:2006-07-27 18:04:26 PDT>PANIC: could not open relation = > 1663/128873/129201: No such file or directory > <4981:2006-07-27 18:04:26 PDT>LOG: startup process (PID 4983) was = > terminated by signal 6 That's really strange ... it's not supposed to be possible to get that error during xlog replay, because XLogOpenRelation is always willing to create a file that doesn't exist. Can you get a stack trace from the crash dump this presumably left behind? If you're just in a panic to get the DB up again, I'd try creating the mentioned file ("touch $PGDATA/base/128873/129201") and see if it'll start. But if you have some time to investigate, it'd be good to try to determine exactly what went wrong here. regards, tom lane