Jamie Echlin wrote: > I was planning to rely on the disk backup (of the base backup) if I wanted to > restore to a version > before the last on disk base backup. But your point about redundancy is > good... I think I will keep > two base backups, and do a base backup every day. Over the network this takes > 5-10 mins or so, so not > a big deal. > > I'll retain wals for 48 hours. Having to go to a PIT before the last hour or > so would be a major > undertaking anyway.
I have seen cases where a software bug in the application gradually caused data in the database to be changed. It took a while to notice that. In such a case you want to have a backup from a month ago or more so that you can extract the data as they were back then and try to repair as much as possible. Also, what if a problem was introduced right before the weekend and noticed immediately afterwards? That might be more than 48 hours ago. There are other scenarios where a backup from longer ago would really help. Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
