Re: Too high rate of progress information from pg_basebackup

On Wed, May 25, 2016 at 12:37 PM, hubert depesz lubaczewski <
depesz(at)depesz(dot)com> wrote:

> Hi,
> it looks that pg_basebackup, when using --progress information, outputs
> so much information that it puts cpu pressure on terminal application
> I'm using - whether it's simple xterm/rxvt, "screen" or "tmux" terminal
> multiplexers.
>
> My specific usecase is setting multiple slave servers for multiple
> clusters in AWS, so the data transmission between servers is pretty
> fast, but the jump host, that I run all the pg_basebackup (via ssh)
> from, is not really beefy, and with 4 concurrent pg_basebackups, I've
> seen tmux use up to 80% of CPU of the jump host.
>
> I filled bug report for tmux too, but since the problem can be repeated
> in xterm, rxvt, and screen, I think that perhaps it should be handled in
> some way in pg_basebackup too?
>
> For completeness sake:
> we're using pg_basebackup from 9.3.11 on ubuntu trusty.
>
> In my quick sanity-check test, it looks that progress information in our
> case is outputted with the speed of ~ 320KB/s. Which seems excessive.
>

Hi!

This was fixed in pg_basebackup in 9.4, see commit
8198a321c9ea2072c5acde438f4d19638e04f6f2.

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/