pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chad Wagner <chad.wagner@gmail.com>
To: Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
Cc: Eduardo J. Ortega <ejortegau@cable.net.co>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL files backup
Date: Fri, 16 Feb 2007 17:32:28 -0500
Message-ID: <81961ff50702161432v5e77a806odc7b5143d7f8113f@mail.gmail.com> (raw)
In-Reply-To: <45D5C8A9.8090002@mailnetwork.co.uk>
References: <945295.11491.qm@web55414.mail.re4.yahoo.com>
	<200702152235.57473.ejortegau@cable.net.co>
	<81961ff50702160334x411e3aeau76ca57c628e0f45e@mail.gmail.com>
	<45D5C8A9.8090002@mailnetwork.co.uk>

On 2/16/07, Andy Shellam (Mailing Lists) <
andy.shellam-lists@mailnetwork.co.uk> wrote:
>
>
> Why bother trying to delete WAL files older than the .backup file?  When
> PostgreSQL is in recovery mode it knows which WAL files are necessary to
> perform the recovery.
>
> Also, the documentation recommends excluding the pg_xlog directory when
> performing the base backup.  Likely when it comes time to recovery the
> online WAL files have been archived already, so it is a risk of confusion I
> am sure.
>
>
> If the OP is doing the same as myself, the WAL files are being archived
> outside of pg_xlog (indeed outside of the PG data cluster) - it makes no
> sense keeping around WAL files older than the .backup file because they're
> not needed - in a day I generate ~5GB worth of WAL files which aren't needed
> after the full backup runs at 2am, so it's a waste of resources to keep them
> around or to worry about backing them up after this time.
>


I mentioned this in my other response, the only reason I ask is because of
the potential need to recover from an earlier base backup up to a specific
point -- perhaps before the most recent base backup.  Personally I don't
think it is a good idea for every environment to do this, but I can see the
value in it and if you truly feel it is unnecessary then I can certainly
respect that.  Perhaps I am a bit too paranoid :), but I have seen people
foolishly do a huge cleanup and then take a backup and realize "Oh crap, I
did too much!" -- and if you don't have all the WAL files you certainly
can't guarantee a specific PITR.


-- 
Chad
http://www.postgresqlforums.com/

view thread (18+ messages)  latest in thread

Message-ID: <81961ff50702161432v5e77a806odc7b5143d7f8113f@mail.gmail.com>
Permalink:  ../81961ff50702161432v5e77a806odc7b5143d7f8113f@mail.gmail.com/
Also on:    postgresql.org/message-id/81961ff50702161432v5e77a806odc7b5143d7f8113f@mail.gmail.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 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: chad.wagner@gmail.com, andy.shellam-lists@mailnetwork.co.uk, ejortegau@cable.net.co
  Subject: Re: WAL files backup
  In-Reply-To: <81961ff50702161432v5e77a806odc7b5143d7f8113f@mail.gmail.com>
  References: <945295.11491.qm@web55414.mail.re4.yahoo.com> <200702152235.57473.ejortegau@cable.net.co> <81961ff50702160334x411e3aeau76ca57c628e0f45e@mail.gmail.com> <45D5C8A9.8090002@mailnetwork.co.uk> <81961ff50702161432v5e77a806odc7b5143d7f8113f@mail.gmail.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