Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BBEED9FA15E for ; Fri, 2 Nov 2007 12:15:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 39638-01 for ; Fri, 2 Nov 2007 12:15:16 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by postgresql.org (Postfix) with ESMTP id 2B9209FA151 for ; Fri, 2 Nov 2007 12:15:15 -0300 (ADT) Received: by nf-out-0910.google.com with SMTP id f5so638028nfh for ; Fri, 02 Nov 2007 08:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:references; bh=AydArjdetyaXxi+NtRTr23ablVebCKFHnOhvtK2QHAk=; b=dz2wIZ+tBV4rKHe4N7DALfu9bURHVfr1fbGUmrZPEmoY4s4CMhCS4V+IxVvbFFsZreKA4wiv07ebxQyGfc+ubvHR5DoK4ACCNK6yOo2gIkR8P1pyXIUOJ6zBb6oueR7RrUixGPy+wv1et6NLPpRu7VR5J2spR+prVe1Zf87z5w0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:references; b=NYuDUD0XEw0x631H6HrkHWQajo2UgbuymM+/pg9m98b9Pd84TGcCTaxEh4GpW7OkJTZiOU9RHtxl87G9FDSW33qENaPZBc9eQ5qmAerL0hLzBtZ5S5lCvgAYmRajDiCGm0B+WJqA3CmRDmgPviTacqvVxU/pFPOGPViQ8he9/1M= Received: by 10.78.159.7 with SMTP id h7mr1397459hue.1194016514670; Fri, 02 Nov 2007 08:15:14 -0700 (PDT) Received: by 10.78.146.6 with HTTP; Fri, 2 Nov 2007 08:15:14 -0700 (PDT) Message-ID: Date: Fri, 2 Nov 2007 15:15:14 +0000 From: "Peter Childs" Subject: Re: jumpstart - pgsql.v824 Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_18888_29565306.1194016514665" References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/24 X-Sequence-Number: 27267 ------=_Part_18888_29565306.1194016514665 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 02/11/2007, dx k9 wrote: > > Hi Everyone, > > 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_twophas= e, > but no pg_xlog? > > 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. > > I'm going to start experimenting and testing to see if I can trick it to > starting, but if anyone has any insight that would help. We noticed this= on > a test restore, so it wasn't a major problem, now we are backing up the > pg_xlog files as well. > > ~DjK > > > ------------------------------ > Windows Live Hotmail and Microsoft Office Outlook =96 together at last. G= et > it now! > Please reread the instructions on pitr and then create an empty pg_xlog directory it can then be filled using what ever you have set "restore_command" to. I guess thats what you want to achieve? Peter. ------=_Part_18888_29565306.1194016514665 Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

On 02/11/2007, dx k9 <bits= andbytes88@hotmail.com> wrote:
Hi Everyone,

Is there any way to trick an instance into starting whe= n you just have base, global, pg_clog, pg_mulitxact, pg_subtrans, pg_tblspc= , & pg_twophase, but no pg_xlog?

 We weren't backing up= the pg_xlog, because we didn't think we needed it, but the backup_labe= l seems to need it.  Even if we take the backup_label file out, and tr= y to start postgres, it doesn't start.

I'm going to start experimenting and testing to see if I can tr= ick it to starting, but if anyone has any insight that would help.  We= noticed this on a test restore, so it wasn't a major problem, now we a= re backing up the pg_xlog files as well.

~DjK



Windows Live Hotmail and Mic= rosoft Office Outlook =96 together at last. Get it now!

Please reread the instructions on pitr and th= en create an empty pg_xlog directory it can then be filled using what ever = you have set "restore_command" to.
I guess thats what you want= to achieve?

Peter.
------=_Part_18888_29565306.1194016514665--