Postgres Pro
Downloads
Home   >   mailing lists

Re: PITR Multiple recoveries - Mailing list pgsql-general

From Sébastien Boutté
Subject Re: PITR Multiple recoveries
Date
Msg-id CAOP64UpN6Y2tqROCp2d0OP72JdguGwqTEm_TcMJUL+F6XT0F_Q@mail.gmail.com
Whole thread Raw
In response to Re: PITR Multiple recoveries  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general
Tree view
Hi Jeff,

You mean that  ? Is this correct ?
hot_stanby = on to be sure it plays WAL and stays in standby mode ?

1. Stop Postgres
2. Restore Local basebackup (untar, un gzip)
3. Create (recovery.conf) standby_mode + hot_standby on (postgresql.conf)
4. Start Postgres
5. Wait to see in log "database system is ready to accept read only connections"
6. To Check
7. Stop Postgres
8. ..... some time passed
9. resync wals with latest
10. recreate recovery.conf without standby_mode + hot_standby off
11. Start Postgres
11. Wait recovery.done
12. To Check

Thanks

Sebastien




On Thu, Feb 8, 2018 at 5:11 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
On Thu, Feb 8, 2018 at 5:07 AM, Sébastien Boutté <sebastien.boutte@gmail.com> wrote:
Hi all,

I'm trying to make my server doing PITR backup, i follow the rules on 

On my local server, i would like to resync multiple times my local database:

What i'm doing :
1. Stop Postgres
2. Restore Local basebackup (untar, un gzip)
3. Create recovery.conf
4. Start Postgres
5. Wait recovery.done
6. At this point, it's OK.

Once recovery is done and the database is open, it is now a primary.  It is no longer eligible for further WAL replay.
(Unless it is was only open in standby mode.)
  
Cheers,

Jeff

pgsql-general by date:

Previous
From: Steven Hirsch
Date:
Subject: Re: Odd behavior with 'currval'
Next
From: Thomas Kellerer
Date:
Subject: Re: DOW is 0-based?