On Tue, Nov 10, 2009 at 11:03 AM, Alban Hertroys <dal...@solfertje.student.utwente.nl> wrote: > IMHO The simplest solution is to just write a dump to the same file every > now and then and have the backup software take care of storing only the > differences. It does have a few drawbacks; it means you'll have a file about > as large as your database on your filesystem just for making backups and > there is a risk that your backup software kicks in before the dump has > finished writing. > > As others mentioned, you can also go with a PITR solution, which is probably > prettier but is a bit harder to set up.
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. -- greg -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
