| 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-22 01:56:10 |
| Message-ID: | ed87ee48-d166-80ff-3eb3-6524cab38e5a@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| fix_pg_basebackup_doc_v4.patch | text/plain | 1.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2021-04-22 01:59:58 | Re: WIP: WAL prefetch (another approach) |
| Previous Message | Andres Freund | 2021-04-22 01:34:11 | Re: WIP: WAL prefetch (another approach) |