pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: restoring wal archive and pg_xlog dir
Date: Thu, 23 Jun 2005 22:40:44 +0100
Message-ID: <1119562844.3645.549.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.63.0506231054250.21285@discord.dyndns.org>
References: <Pine.LNX.4.63.0506231054250.21285@discord.dyndns.org>

On Thu, 2005-06-23 at 10:55 -0700, Jeff Frost wrote:
> When reading the docs on recovery.conf, I noticed this:
> 
>   WAL segments that cannot be found in the archive will be sought in pg_xlog/; 
> this allows use of recent un-archived segments. However segments that are 
> available from the archive will be used in preference to files in pg_xlog/. The 
> system will not overwrite the existing contents of pg_xlog/ when retrieving 
> archived files.
> 
> If the system will use the files in the archive in preference to the ones in 
> pg_xlog, how can this actually happen if it will not overwrite the contents of 
> pg_xlog?

That was the bit I thought of. The files are streamed in one by one using a temp filename, so you never run out of space no matter how big the archive of transaction logs. Thats an important feature if a base backup goes bad and you have to go back to n-1 base backup.

> I also noticed that if there is not at least one wal archive available in
> the archive or the pg_xlog dir, the restore errors out and exits.  So the
> base backup is really not complete without at least one wal archive
> following it.  Is this by design?

That was the bit I didn't. Fix partially implemented and I am to submit
for 8.1, godspeed my typing fingers. There's a simple workaround if you
have a low transaction rate system: load up enough data to trip into the
next xlog.

Best Regards, Simon Riggs




view thread (11+ messages)  latest in thread

Message-ID: <1119562844.3645.549.camel@localhost.localdomain>
Permalink:  ../1119562844.3645.549.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1119562844.3645.549.camel@localhost.localdomain

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: simon@2ndquadrant.com, jeff@frostconsultingllc.com
  Subject: Re: restoring wal archive and pg_xlog dir
  In-Reply-To: <1119562844.3645.549.camel@localhost.localdomain>
  References: <Pine.LNX.4.63.0506231054250.21285@discord.dyndns.org> <1119562844.3645.549.camel@localhost.localdomain>

* 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