| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | "Shinoda, Noriyoshi (PN Japan A&PS Delivery)" <noriyoshi(dot)shinoda(at)hpe(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "amitlangote09(at)gmail(dot)com" <amitlangote09(at)gmail(dot)com>, "masahiko(dot)sawada(at)2ndquadrant(dot)com" <masahiko(dot)sawada(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_stat_progress_basebackup - progress reporting for pg_basebackup, in the server side |
| Date: | 2020-03-05 07:15:28 |
| Message-ID: | 424e015a-ee68-ca8a-ea67-8ee1473d7523@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2020-03-05 07:26:55 | Re: PG_COLOR not mentioned in docs of vacuumlo, oid2name and pgbench |
| Previous Message | Kyotaro Horiguchi | 2020-03-05 07:06:50 | Re: Make mesage at end-of-recovery less scary. |