Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id DE1BF9FA152 for ; Fri, 2 Nov 2007 12:25:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 25574-08 for ; Fri, 2 Nov 2007 12:25:04 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 90A939FA14E for ; Fri, 2 Nov 2007 12:25:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lA2FP1d8029788; Fri, 2 Nov 2007 11:25:02 -0400 (EDT) To: dx k9 cc: pgsql-admin@postgresql.org Subject: Re: jumpstart - pgsql.v824 In-reply-to: References: Comments: In-reply-to dx k9 message dated "Fri, 02 Nov 2007 10:11:28 -0400" Date: Fri, 02 Nov 2007 11:25:01 -0400 Message-ID: <29787.1194017101@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/26 X-Sequence-Number: 27269 dx k9 writes: > Is there any way to trick an instance into starting when you just have base, global, pg_clog, pg_mulitxact, pg_subtrans, pg_tblspc, & pg_twophase, but no pg_xlog? pg_resetxlog would probably be enough to get it to start, but the odds of having a non-corrupt database afterwards don't seem very good. > We weren't backing up the pg_xlog, because we didn't think we needed it, but the backup_label seems to need it. Even if we take the backup_label file out, and try to start postgres, it doesn't start. Have you read the manual's chapter on backup/restore? There are several documented ways to do things successfully, but inventing your own is not likely to work. regards, tom lane