Re: pg_stat_progress_basebackup - progress reporting for pg_basebackup, in the server side

From: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_progress_basebackup - progress reporting for pg_basebackup, in the server side
Date: 2020-02-17 13:00:15
Message-ID: f6913955-4597-c66a-0c95-8bedb09057d9@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020/02/06 11:07, Amit Langote wrote:
> On Thu, Feb 6, 2020 at 9:51 AM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
>>> On Wed, Feb 5, 2020 at 18:25 Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
>>>> So, maybe you're saying that "waiting for checkpoint" is ambiguous and
>>>> most people will assume it means "...to start". As for me, I assume
>>>> it ends with "...to finish".
>>
>> I'm not sure "most peple will assume" or not, so I said "I'm not
>> sure". For example, I feel strangeness to use "I'm waiting for Amit"
>> to express that I'm waiting Amit to leave there. That phrase gives me
>> such kind of uneasiness.
>>
>> I thought of "establishing checkpoint" or "running a checkpoint" as
>> other candidates.
>
> Okay, I understand. I am fine with "running checkpoint", although I
> think "waiting for checkpoint" isn't totally wrong either.

Yeah, but if "waiting for XXX" sounds a bit confusing to some people,
I'm OK to back to "waiting for XXX to finish" that you originally
proposed.

Attached the updated version of the patch. This patch uses the following
descriptions of the phases.

waiting for checkpoint to finish
estimating backup size
streaming database files
waiting for wal archiving to finish
transferring wal files

Regards,

--
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters

Attachment Content-Type Size
pg_stat_progress_basebackup_v4.patch text/plain 21.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-02-17 13:01:30 Re: pg_stat_progress_basebackup - progress reporting for pg_basebackup, in the server side
Previous Message Daniel Gustafsson 2020-02-17 12:06:21 Re: tiny documentation fix