pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Kempter <kevin@kevinkempterllc.com>
To: pgsql-admin@postgresql.org
Subject: Re: Understanding wal segments
Date: Thu, 1 Nov 2007 23:38:13 -0600
Message-ID: <200711012338.13229.kevin@kevinkempterllc.com> (raw)
In-Reply-To: <22325.1193981928@sss.pgh.pa.us>
References: <200711012155.16409.kevin@kevinkempterllc.com>
	<200711012239.07980.kevin@kevinkempterllc.com>
	<22325.1193981928@sss.pgh.pa.us>

On Thursday 01 November 2007 23:38:48 Tom Lane wrote:
> Kevin Kempter <kevin@kevinkempterllc.com> writes:
> > Also I suspect after each filesystem backup I should remove the older
> > archived segments since the file system backup makes them
> > irrelevant. Is this accurate?
>
> Depends what your goals are.  If you only want to be able to recover
> the latest database state then you only need archived WAL segments
> back to the start of the latest filesystem backup.  If you are
> interested in the "PITR" aspect of it --- being able to revert back
> to last Tuesday before some bad guy injected bad data, say --- then
> you'll want to keep older filesystem backups too, and a continuous
> string of archived WAL files covering the period of interest.
>
> 			regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster

Makes sense. Thanks.

One more question. I see a fair amount of file changed warnings in the tar 
output. Like this:

tar: ./data/base/82097725/4242350944: file changed as we read it
./data/base/82097725/143763179
./data/base/82097725/3587685114
./data/base/82097725/3587684991
./data/base/82097725/3587685046
./data/base/82097725/3587685003
./data/base/82097725/3588484372
tar: ./data/base/82097725/3588484372: file changed as we read it
./data/base/82097725/3587685172
./data/base/82097725/10733
./data/base/82097725/3588482971
./data/base/82097725/4082992388
./data/base/82097725/4242349291.4
tar: ./data/base/82097725/4242349291.4: file changed as we read it


Is this an issue or does postgres comensate for this since it knows I'm 
running a backup (i've run a pg_start_backup) ?

Thx

/Kevin




view thread (7+ messages)  latest in thread

Message-ID: <200711012338.13229.kevin@kevinkempterllc.com>
Permalink:  ../200711012338.13229.kevin@kevinkempterllc.com/
Also on:    postgresql.org/message-id/200711012338.13229.kevin@kevinkempterllc.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: kevin@kevinkempterllc.com
  Subject: Re: Understanding wal segments
  In-Reply-To: <200711012338.13229.kevin@kevinkempterllc.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