Re: Too high rate of progress information from pg_basebackup - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: Too high rate of progress information from pg_basebackup
Date
Msg-id CAB7nPqSzomYC6cCdz1G6uunFZ4gFEp-j=RzBEJ-PGZ+26-ZrFg@mail.gmail.com
Whole thread Raw
In response to Re: Too high rate of progress information from pg_basebackup  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-bugs
On Wed, May 25, 2016 at 3:58 AM, hubert depesz lubaczewski
<depesz@depesz.com> wrote:
> On Wed, May 25, 2016 at 12:56:18PM +0200, Magnus Hagander wrote:
>> IIRC that was discussed at the time and we decided not to.
>
> Fair enough.

FWIW, there is one conflict at the top of pg_basebackup.c with a set
of variables declared: last_progress_report should be declared as
non-static for consistency. So that's rather minimal.
--
Michael

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #14156: Password Autehentication
Next
From: Marco Nenciarini
Date:
Subject: Re: [HACKERS] BUG #13473: VACUUM FREEZE mistakenly cancel standby sessions