Re: PostgreSQL Point In Time Recovery - Mailing list pgsql-general

From Jeff Janes
Subject Re: PostgreSQL Point In Time Recovery
Date
Msg-id CAMkU=1yLU90dz_9vJqxs4Nm7jj9sKNH0JbGwCW60Z0fenhxWEA@mail.gmail.com
Whole thread Raw
In response to PostgreSQL Point In Time Recovery  (Jayadevan M <maymala.jayadevan@gmail.com>)
Responses Re: PostgreSQL Point In Time Recovery
Re: PostgreSQL Point In Time Recovery
List pgsql-general
On Wed, Oct 23, 2013 at 9:10 PM, Jayadevan M <maymala.jayadevan@gmail.com> wrote:
and set up the archiving process. With this approach, if my database crashes after a couple of weeks after the base backup is taken, recovering would mean replaying the WAL logs for about 2 weeks, right? To avoid that, what is the standard process followed - take a base backup every day or once a week?
Regards,
Jayadevan

I restore from my base backup plus WAL quite often.  It is how I get a fresh dev or test instance when I want one.  (It is also how I have confidence that everything is working well and that I know what I'm doing should the time come to do a real restore).  When that starts to take an annoyingly long time, I run a new base backup.  How often that is, can be anywhere from days to months, depending on what's going on in the database.

Cheers,

Jeff

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: GIST index : order Hack : getting the order used by CLUSTER .. USING my_index
Next
From: Rémi Cura
Date:
Subject: Re: GIST index : order Hack : getting the order used by CLUSTER .. USING my_index