On 2020/03/18 22:37, Atsushi Torikoshi wrote:
On Wed, Mar 18, 2020 at 6:59 PM Fujii Masao mailto:masao.fu...@oss.nttdata.com>> wrote:
I meant the following part in the doc.
-
At startup, the standby begins by restoring all WAL available in the archive
lo
On Wed, Mar 18, 2020 at 6:59 PM Fujii Masao
wrote:
>
> I meant the following part in the doc.
>
> -
> At startup, the standby begins by restoring all WAL available in the
> archive
> location, calling restore_command. Once it reaches the end of WAL available
> there and restor
On 2020/03/18 17:56, Atsushi Torikoshi wrote:
On Tue, Mar 17, 2020 at 11:55 AM Fujii Masao mailto:masao.fu...@oss.nttdata.com>> wrote:
> > Waiting when WAL data is not available from any kind of sources
> > (local, archive or stream) before trying again to retrieve WAL
dat
On Tue, Mar 17, 2020 at 11:55 AM Fujii Masao
wrote:
> > >Waiting when WAL data is not available from any kind of sources
> > >(local, archive or stream) before trying again to retrieve WAL
> data,
> >
> > I think 'local' means pg_wal here, but the comment on
> > WaitForWALToBecomeAvaila
On 2020/03/15 0:06, Atsushi Torikoshi wrote:
On 2020/02/19 21:46 Fujii Masao mailto:masao.fu...@oss.nttdata.com>>:
>> I agree to the former, I think RecoveryWalInterval works well enough.
>RecoveryWalInterval sounds confusing to me...
IMHO as a user, I prefer RecoveryRetrieveRetryInterval b
On 2020/02/19 21:46 Fujii Masao :
>> I agree to the former, I think RecoveryWalInterval works well enough.
>RecoveryWalInterval sounds confusing to me...
IMHO as a user, I prefer RecoveryRetrieveRetryInterval because
it's easy to understand this wait_event is related to the
parameter 'wal_retrieve
On 2020/02/18 14:20, Kyotaro Horiguchi wrote:
Hello.
At Tue, 18 Feb 2020 12:25:51 +0900, Fujii Masao
wrote in
Hi,
RecoveryWalAll and RecoveryWalStream wait events are documented as
follows.
RecoveryWalAll
Waiting for WAL from any kind of source (local, archive or stream) at
Hello.
At Tue, 18 Feb 2020 12:25:51 +0900, Fujii Masao
wrote in
> Hi,
>
> RecoveryWalAll and RecoveryWalStream wait events are documented as
> follows.
>
> RecoveryWalAll
> Waiting for WAL from any kind of source (local, archive or stre
Hi,
RecoveryWalAll and RecoveryWalStream wait events are documented as follows.
RecoveryWalAll
Waiting for WAL from any kind of source (local, archive or stream) at
recovery.
RecoveryWalStream
Waiting for WAL from a stream at recovery.
But as far as I read the code
