pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: George Wilk <gwilk@ellacoya.com>
To: 'Simon Riggs' <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: missing history file
Date: Fri, 29 Jun 2007 09:57:25 -0400
Message-ID: <00af01c7ba55$6c96b0f0$0d7ba8c0@ellacoya.com> (raw)
In-Reply-To: <1183124513.3589.104.camel@silverbirch.site>

Thanks, Simon.  I will ignore the request for the history file in my
recovery_command from now on.

Is the timeline history file needed when trying to put the standby server
back into the recovery mode, after it assumed the primary role?  (i.e.
standby server goes *live*, and is subsequently restarted in the recovery
mode).  Is this a valid scenario at all, or should I be taking a new base
backup and starting over?  I am running into some problems when attempting
this.

~george

-----Original Message-----
From: Simon Riggs [mailto:simon@2ndquadrant.com] 
Sent: Friday, June 29, 2007 9:42 AM
To: George Wilk
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] missing history file

On Fri, 2007-06-29 at 07:55 -0400, George Wilk wrote:

> My warm standby server is looking for a history file when booting up.
> It is looking for 00000001.history file to be exact. 

Just ignore 00000001. Recovery will work fine even if absent. Don't
ignore all history files though, just that one. Hmmm, come to think of
it, why is it requesting it at all? We should just skip that request.

>  Since my *live* server doesn't produce such file, I create an empty
> 00000001.history file in the archive directory and that seems to
> satisfy this requirement allowing the standby server to come up in the
> recovery mode.  

Well, that should at least generate a message that says "history file
empty, using targetTLI".

> It would be nice to know though how such file is created.  I know that
> the *live* server creates *.backup file as a result of
> pg_stop_backup() command and this file is accurately archived on the
> standby server.  Should I be renaming this file, or is there some
> other mechanism to tell my standby server what the history file is?

The timeline history file is only required when you do a recovery of a
system that has itself already undergone a PITR.

Have a look at pg_standby, accessible via CVS in contrib/pg_standby.

-- 
  Simon Riggs             
  EnterpriseDB   http://www.enterprisedb.com







view thread (12+ messages)  latest in thread

Message-ID: <00af01c7ba55$6c96b0f0$0d7ba8c0@ellacoya.com>
Permalink:  ../00af01c7ba55$6c96b0f0$0d7ba8c0@ellacoya.com/
Also on:    postgresql.org/message-id/00af01c7ba55$6c96b0f0$0d7ba8c0@ellacoya.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: gwilk@ellacoya.com, simon@2ndquadrant.com
  Subject: Re: missing history file
  In-Reply-To: <00af01c7ba55$6c96b0f0$0d7ba8c0@ellacoya.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox