| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> | 
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> | 
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: pg_basebackup wish list | 
| Date: | 2016-07-13 12:08:28 | 
| Message-ID: | CAA4eK1LbfuvcCewM73izkfWOKccr=DZf=pceAeXmiLxkrN86Sw@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
On Tue, Jul 12, 2016 at 10:23 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> I've been having some adventures with pg_basebackup lately, and had
> some suggestions based on those.
>
> The --help message for pg_basebackup says:
>
> -Z, --compress=0-9     compress tar output with given compression level
>
> But -Z0 is then rejected as 'invalid compression level "0"'.  The real
> docs do say 1-9, only the --help message has this bug.  Trivial patch
> attached.
>
> These ones I have not written code for yet:
>
> The progress reporting for pg_basebackup is pretty terse:
>
>  858117/7060099 kB (12%), 0/1 tablespace
>
> I think we should at least add a count-up timer showing the seconds it
> has been running.  I can always use my own stopwatch, but that is not
> very friendly and easy to forget to start.
>
Another possibility is to enhance -P option as -P sec, such that it
will display progress after ever 'sec' seconds.  Something like we
have for pgbench.
-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Netanel Katzburg | 2016-07-13 12:23:17 | Re: Disable WAL completely - Performance and Persistency research | 
| Previous Message | Amit Kapila | 2016-07-13 11:27:48 | Re: Simplifying the interface of UpdateMinRecoveryPoint |