Re: Stale description for pg_basebackup

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: masao(dot)fujii(at)oss(dot)nttdata(dot)com
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Stale description for pg_basebackup
Date: 2021-04-22 04:25:27
Message-ID: 20210422.132527.374548856273385613.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 22 Apr 2021 13:06:50 +0900, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote in
> Either works for me. I didn't add "()" because I just used the same
> description
> as that in func.sgml.
>
> it may be useful to run <function>pg_switch_wal</function> on the
> primary in order to trigger an immediate segment switch.)
..
> IMO "in order to..." part is helpful for us to understand why
> pg_switch_wal
> is useful in this case. So I'd like to leave it.

Ok, I'm fine with both of them. Thanks for the explanation.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Biryukov 2021-04-22 04:30:41 Re: posgres 12 bug (partitioned table)
Previous Message Dilip Kumar 2021-04-22 04:13:23 Re: Replication slot stats misgivings