| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Stale description for pg_basebackup |
| Date: | 2021-04-23 06:53:02 |
| Message-ID: | bcaf6264-0a1d-42a7-88bf-8d04bfb10c59@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/04/22 13:25, Kyotaro Horiguchi wrote:
> 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.
Pushed. Thanks!
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Jacobson | 2021-04-23 06:54:45 | Re: pg_identify_object_as_address() doesn't support pg_event_trigger oids |
| Previous Message | Amul Sul | 2021-04-23 06:51:07 | Re: fix a comment |