Re: WAL and pg_dump

From: Mike C <smith(dot)not(dot)western(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: WAL and pg_dump
Date: 2005-12-22 21:09:28
Message-ID: bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 12/22/05, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
> On Tue, 2005-12-13 at 11:18 +1300, Mike C wrote:
> > All the documentation I've seen for PITR points to having to do a file
> > system copy of sorts.
>
> Yes. There's no other way, but why would you want another way?

Mainly because a pg_dump backup takes up a lot less disk space than a
filesystem copy (in my case, approx 3.5GB backup from a 25GB db).

> Is it possible to have a weekly pg_dump and restore the database up to
> > the last archived WAL file if the db server fails?
>
> No.
>
> pg_dump only copies the data, not the current state of the database.

I guess if pg_dump was modified to record the last complete transaction id
(in archive format maybe) then the WAL files could be used?

Thanks for the response,

Mike C.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Simon Riggs 2005-12-22 22:17:32 Re: WAL and pg_dump
Previous Message Mike C 2005-12-22 20:58:20 Create Index Locking Question