From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Atsushi Torikoshi <atorik@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: RecoveryWalAll and RecoveryWalStream wait events
Date: Tue, 17 Mar 2020 11:55:43 +0900
Message-ID: <aab7b94f-8140-48eb-3e31-698be55275d5@oss.nttdata.com> (raw)
In-Reply-To: <CACZ0uYE1UJomZ1tiB1vLwJSo_a2HAoXA6AF4=GRNfEkz-J1kNA@mail.gmail.com>
References: <124997ee-096a-5d09-d8da-2c7a57d0816e@oss.nttdata.com>
<20200218.142016.2107516686265665330.horikyota.ntt@gmail.com>
<2ea0c6f1-adcd-f2a2-fe5a-92376ad38432@oss.nttdata.com>
<CACZ0uYE1UJomZ1tiB1vLwJSo_a2HAoXA6AF4=GRNfEkz-J1kNA@mail.gmail.com>
On 2020/03/15 0:06, Atsushi Torikoshi wrote:
> On 2020/02/19 21:46 Fujii Masao <masao.fujii@oss.nttdata.com <mailto:masao.fujii@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 because
> it's easy to understand this wait_event is related to the
> parameter 'wal_retrieve_retry_interval'.
>
> Also from the point of balance, the explanation of
> RecoveryRetrieveRetryInterval is lengthy, but I
> sometimes feel explanations of wait_events in the
> manual are so simple that it's hard to understand
> well.
+1 to document them more. It's not easy task, though..
> > 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
> WaitForWALToBecomeAvailable() says checking pg_wal in
> standby mode is 'not documented', so I'm a little bit worried
> that users may be confused.
This logic seems to be documented in high-availability.sgml.
But, anyway, you think that "pg_wal" should be used instead of "local" here?
Regards,
--
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters
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-hackers@postgresql.org
Cc: masao.fujii@oss.nttdata.com, atorik@gmail.com, horikyota.ntt@gmail.com
Subject: Re: RecoveryWalAll and RecoveryWalStream wait events
In-Reply-To: <aab7b94f-8140-48eb-3e31-698be55275d5@oss.nttdata.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