Skip site navigation (1) Skip section navigation (2)

Re: Backup of live database

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Tom Davies" <tgdavies(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Backup of live database
Date: 2008-01-16 23:27:34
Message-ID: dcc563d10801161527s39b3e3adm566357813f4b9a13@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Jan 16, 2008 4:56 PM, Tom Davies <tgdavies(at)gmail(dot)com> wrote:
>
> On 17/01/2008, at 4:42 AM, Tom Arthurs wrote:
> > The important thing is to start archiving the WAL files *prior* to
> > the first OS backup, or you will end up with an unusable data base.
>
> Why does the recovery need WAL files from before the backup?

It's a timeline thing.  The database is coherent at time x1.  The wal
file started at point x0 and moving forward, at some point, matches
up.  You run the start_archive command which tells pgsql you're
starting your backup at point x1.  You start the backup.  You now have
a backup of the pgsql datastore that's a mix of what you had at x1
when you started, and x2 where you stopped.

You apply the WAL from x0 forward to, say x3., and it conveniently
rewrites the datastore to be coherent.  If your WAL was from some
point between x1 and x2 you might have some data in the database that
the WAL file wouldn't write over, but was incoherent in regards to
what you'd get from point x3.  So, some pages now are out of date,
because your WAL file isn't old enough.

In response to

pgsql-admin by date

Next:From: Tom ArthursDate: 2008-01-17 01:02:00
Subject: Re: Backup of live database
Previous:From: Tom LaneDate: 2008-01-16 23:26:30
Subject: Re: Backup of live database

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group