Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side
Date
Msg-id 424e015a-ee68-ca8a-ea67-8ee1473d7523@2ndquadrant.com
Whole thread Raw
In response to Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side  (Julien Rouhaud <rjuju123@gmail.com>)
Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Tree view 
On 2020-03-05 05:53, Fujii Masao wrote:
> Or, as another approach, it might be worth considering to make
> the server always estimate the total backup size whether --progress is
> specified or not, as Amit argued upthread. If the time required to
> estimate the backup size is negligible compared to total backup time,
> IMO this approach seems better. If we adopt this, we can also get
> rid of PROGESS option from BASE_BACKUP replication command.

I think that would be preferable.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Make mesage at end-of-recovery less scary.
Next
From: Michael Paquier
Date:
Subject: Re: PG_COLOR not mentioned in docs of vacuumlo, oid2name and pgbench