Re: Stronger safeguard for archive recovery not to miss data

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, 'Kyotaro Horiguchi' <horikyota(dot)ntt(at)gmail(dot)com>
Cc: "david(at)pgmasters(dot)net" <david(at)pgmasters(dot)net>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "laurenz(dot)albe(at)cybertec(dot)at" <laurenz(dot)albe(at)cybertec(dot)at>
Subject: Re: Stronger safeguard for archive recovery not to miss data
Date: 2021-04-06 11:13:49
Message-ID: d4dc656f-8eab-ecf2-4ad4-b4d4e1b317e1@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2021/04/06 15:59, osumi(dot)takamichi(at)fujitsu(dot)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 at first.
Then we can improve the docs if required.

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2021-04-06 11:19:26 Re: pgbench - add pseudo-random permutation function
Previous Message Pavel Borisov 2021-04-06 11:09:59 Re: [PATCH] Covering SPGiST index