Re: Too high rate of progress information from pg_basebackup

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: depesz(at)depesz(dot)com
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Postgres Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Too high rate of progress information from pg_basebackup
Date: 2016-05-25 16:38:05
Message-ID: CAB7nPqSzomYC6cCdz1G6uunFZ4gFEp-j=RzBEJ-PGZ+26-ZrFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, May 25, 2016 at 3:58 AM, hubert depesz lubaczewski
<depesz(at)depesz(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Marco Nenciarini 2016-05-25 17:33:12 Re: [HACKERS] BUG #13473: VACUUM FREEZE mistakenly cancel standby sessions
Previous Message Michael Paquier 2016-05-25 16:29:50 Re: BUG #14156: Password Autehentication