Horton

Re: Stale description for pg_basebackup

Fujii Masao <masao.fujii@oss.nttdata.com>

View thread View on postgr.es
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2021-04-22T01:56:10Z
Lists: pgsql-hackers

Attachments


On 2021/04/22 9:25, Kyotaro Horiguchi wrote:
>> What about the following description?
>>
>> -------------------
>> When you are using -X none, if write activity on the primary is low,
>> pg_basebackup may need to wait a long time for all WAL files required
>> for
>> the backup to be archived. It may be useful to run pg_switch_wal
>> on the primary in order to trigger an immediate WAL file switch and
>> archiving.
>> -------------------
> 
> Looks far better.

Patch attached. I appended the following description to assist
users to understand why pg_basebackup may need wait a long time
when write activity is low on the primary.

------------------
pg_basebackup cannot force the standby to switch to
a new WAL file at the end of backup.
------------------

Regards,

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

Commits

  1. doc: Fix obsolete description about pg_basebackup.

  2. Make pg_stop_backup's wait_for_archive flag work on standbys.