| From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, akp geek <akpgeek(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Incremental Backups in postgres |
| Date: | 2009-11-10 16:24:45 |
| Message-ID: | d3ab2ec80911100824n61db3407p93e1ce923c6d5e32@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Nov 10, 2009 at 9:52 AM, Greg Stark <gsstark(at)mit(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-11-10 16:36:03 | Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed |
| Previous Message | Andrei | 2009-11-10 16:06:16 | Re: How can I calculate differences between values |