From: Mike C <smith.not.western@gmail.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL and pg_dump
Date: Fri, 23 Dec 2005 10:09:28 +1300
Message-ID: <bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com> (raw)
In-Reply-To: <1135208028.2964.329.camel@localhost.localdomain>
References: <bd0eabd0512121418h4c39a3e6mc71947264e18656f@mail.gmail.com>
<1135208028.2964.329.camel@localhost.localdomain>
On 12/22/05, Simon Riggs <simon@2ndquadrant.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.
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: smith.not.western@gmail.com, simon@2ndquadrant.com
Subject: Re: WAL and pg_dump
In-Reply-To: <bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com>
References: <bd0eabd0512121418h4c39a3e6mc71947264e18656f@mail.gmail.com> <1135208028.2964.329.camel@localhost.localdomain> <bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@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