Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side
| От | Peter Eisentraut |
|---|---|
| Тема | Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side |
| Дата | |
| Msg-id | 424e015a-ee68-ca8a-ea67-8ee1473d7523@2ndquadrant.com обсуждение |
| Ответ на | Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side (Fujii Masao <masao.fujii@oss.nttdata.com>) |
| Ответы |
Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side
Re: pg_stat_progress_basebackup - progress reporting forpg_basebackup, in the server side |
| Список | 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
В списке pgsql-hackers по дате отправления: