Too high rate of progress information from pg_basebackup

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Postgres Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Too high rate of progress information from pg_basebackup
Date: 2016-05-25 10:37:50
Message-ID: 20160525103750.GA12835@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

Best regards,

depesz

--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2016-05-25 10:52:55 Re: Too high rate of progress information from pg_basebackup
Previous Message digoal 2016-05-25 09:54:02 BUG #14158: PostgreSQL 9.6 bloom don't support unlogged table?