pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sebastian Reitenbach <sebastia@l00-bugdead-prods.de>
Cc: pgsql-admin@postgresql.org
Subject: Re: backup WAL files,
Date: Tue, 15 Jan 2008 17:32:31 +0100
Message-ID: <20080115163232.0E8A93AAA1@smtp.l00-bugdead-prods.de> (raw)

Hi,
Tom Lane <tgl@sss.pgh.pa.us> wrote: 
> "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> writes:
> > The WAL files have names like this:
> > 00000001000000010000003C
> 
> > I am wonder what the meaning of the two 1 in the filename is?
> 
> The first one (the first 8 hex digits actually) are the current
> "timeline" number.  The second one isn't very interesting, it's
> an artifact of the way that WAL file locations are converted to
> file names internally.
thanks for this information.

> 
> > Are the WAL 
> > file names counted up to FFFFFFFFFFFFFFFFFFFFFFFFF ?
> > Then I'll run into problems anyways as these int number are too large to 
be 
> > handled by bash.
> 
> You definitely should not expect to convert the names to integers.

Then I do not understand why only the names of the first and the last WAL 
file are stored in the backup history file. I assumed that when I count from 
the first to the last I catch all WAL files needed for a complete backup.
Then I have no idea how to figure out, which of the WAL files are needed for 
the backup job. Or do I have to handle this via the file modification 
timestamps?

does anybody has a pointer to documentation where I can read up about how 
the names of the WAL files are created/used in postgres?

thanks
Sebastian




view thread (7+ messages)  latest in thread

Message-ID: <20080115163232.0E8A93AAA1@smtp.l00-bugdead-prods.de>
Permalink:  ../20080115163232.0E8A93AAA1@smtp.l00-bugdead-prods.de/
Also on:    postgresql.org/message-id/20080115163232.0E8A93AAA1@smtp.l00-bugdead-prods.de

 · 

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: sebastia@l00-bugdead-prods.de
  Subject: Re: backup WAL files,
  In-Reply-To: <20080115163232.0E8A93AAA1@smtp.l00-bugdead-prods.de>

* 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