Re: Incremental Backups in postgres - Mailing list pgsql-general

From akp geek
Subject Re: Incremental Backups in postgres
Date
Msg-id 2024a9fb0911101349p40ac826i93b1e4fe0a765b37@mail.gmail.com
Whole thread Raw
In response to Re: Incremental Backups in postgres  (Scott Mead <scott.lists@enterprisedb.com>)
Responses Re: Incremental Backups in postgres
List pgsql-general
So Is it always good to have the backup using PG_dump instead of PITR or a combination of both
 
Please advice
 
Regards

On Tue, Nov 10, 2009 at 11:24 AM, Scott Mead <scott.lists@enterprisedb.com> wrote:

On Tue, Nov 10, 2009 at 9:52 AM, Greg Stark <gsstark@mit.edu> wrote:

It's always worth having the dump, even if you also implement PITR.
The dump allows you to restore just specific tables or to restore onto
a different type of system. The PITR backup is a physical
byte-for-byte copy which only works if you restore the whole database
and only on the same type of system.

    Good point here, you really should have a 'logical' copy of your database around in case there is some kind of physical corruption in addition to Greg's good points.

--Scott

pgsql-general by date:

Previous
From: akp geek
Date:
Subject: Re: Incremental Backups in postgres
Next
From: Alan Hodgson
Date:
Subject: Re: Incremental Backups in postgres