Re: Stronger safeguard for archive recovery not to miss data

Fujii Masao <masao.fujii@oss.nttdata.com>

From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: David Steele <david@pgmasters.net>, "osumi.takamichi@fujitsu.com" <osumi.takamichi@fujitsu.com>, 'Kyotaro Horiguchi' <horikyota.ntt@gmail.com>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>, "laurenz.albe@cybertec.at" <laurenz.albe@cybertec.at>
Date: 2021-04-06T14:01:05Z
Lists: pgsql-hackers

On 2021/04/06 20:44, David Steele wrote:
> On 4/6/21 7:13 AM, Fujii Masao wrote:
>>
>> On 2021/04/06 15:59, osumi.takamichi@fujitsu.com wrote:
>>> I just wanted to write why the error was introduced,
>>> but it was not necessary.
>>> We should remove and fix the first part of the sentence.
>>
>> So the consensus is almost the same as the latest patch?
>> If they are not so different, I'm thinking to push the latest version atfirst.
>> Then we can improve the docs if required.
> 
> +1

Thanks! So I pushed the patch.


On 2021/04/06 20:48, osumi.takamichi@fujitsu.com wrote:
> Yes, please. What I suggested is almost same as your idea.

Thanks!

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



Commits

  1. Fix test added by commit 9de9294b0c.

  2. Stop archive recovery if WAL generated with wal_level=minimal is found.