From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Limit pg_basebackup progress output to 1/second |
Date: | 2014-02-09 11:52:07 |
Message-ID: | E1WCSvf-0007dd-8q@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Limit pg_basebackup progress output to 1/second
This prevents pg_basebackup from generating excessive output when
dumping large clusters. The status is now updated once / second,
still making it possible to see that there is progress happening,
but limiting the total bandwidth.
Mika Eloranta, reviewed by Sawada Masahiko and Oskari Saarenmaa
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/8198a321c9ea2072c5acde438f4d19638e04f6f2
Modified Files
--------------
src/bin/pg_basebackup/pg_basebackup.c | 35 +++++++++++++++++++++++----------
1 file changed, 25 insertions(+), 10 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-02-09 13:33:59 | Re: [HACKERS] Viability of text HISTORY/INSTALL/regression README files (was Re: [COMMITTERS] pgsql: Document a few more regression test hazards.) |
Previous Message | Magnus Hagander | 2014-02-09 11:19:00 | pgsql: Avoid printing uninitialized filename variable in verbose mode |