| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Sébastien Boutté <sebastien(dot)boutte(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PITR Multiple recoveries |
| Date: | 2018-02-08 16:11:24 |
| Message-ID: | CAMkU=1zvwf2Vt5tTCoi9-QcwbYYv-VyzS3UbmVun_bLnmO58=w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Feb 8, 2018 at 5:07 AM, Sébastien Boutté <sebastien(dot)boutte(at)gmail(dot)com
> wrote:
> Hi all,
>
> I'm trying to make my server doing PITR backup, i follow the rules on
> https://www.postgresql.org/docs/9.5/static/continuous-archiving.html.
>
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-02-08 16:15:49 | Re: Odd behavior with 'currval' |
| Previous Message | Steven Hirsch | 2018-02-08 16:09:45 | Odd behavior with 'currval' |