From: Euler Taveira <euler@eulerto.com>
To: Gareth Vaughan <gareth@specialisedstructures.co.nz>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: PITR restores incorrect state
Date: Wed, 17 Feb 2021 14:06:00 -0300
Message-ID: <5cf0ba4e-5d4d-40da-b17f-ae37fea9c388@www.fastmail.com> (raw)
In-Reply-To: <001501d704cf$b9979760$2cc6c620$@specialisedstructures.co.nz>
References: <001501d704cf$b9979760$2cc6c620$@specialisedstructures.co.nz>
On Tue, Feb 16, 2021, at 10:53 PM, Gareth Vaughan wrote:
> 10) in an elevated cmd run these:
> net stop postgresql-x64-13
> DEL /F/Q/S "c:\Program Files\PostgreSQL\13\data\*" > NUL
> RMDIR /Q/S "c:\Program Files\PostgreSQL\13\data\"
> mkdir "c:\Program Files\PostgreSQL\13\data\"
> xcopy C:\temp\pitr_test\base_backup\* "c:\Program Files\PostgreSQL\13\data\" /e /q
> icacls "c:\Program Files\PostgreSQL\13\data" /grant postgres:(OI)(CI)F
> net start postgresql-x64-13
>
This is not a bug. Your forgot step 7: create a $PGDATA/recovery.signal [1]. It
was changed in version 12 when the recovery settings was moved to
postgresql.conf.
[1] https://www.postgresql.org/docs/13/continuous-archiving.html#BACKUP-PITR-RECOVERY
--
Euler Taveira
EDB https://www.enterprisedb.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: euler@eulerto.com, gareth@specialisedstructures.co.nz, pgsql-bugs@lists.postgresql.org
Subject: Re: PITR restores incorrect state
In-Reply-To: <5cf0ba4e-5d4d-40da-b17f-ae37fea9c388@www.fastmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox