Re: Too high rate of progress information from pg_basebackup

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Postgres Bugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Too high rate of progress information from pg_basebackup
Date: 2016-05-25 10:58:52
Message-ID: 20160525105852.GA26536@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

> The patch is fairly simple though, it wouldn't surprise me if it applies
> cleanly to 9.3 if you want to do a one-off build. Though I guess that means
> we could also reconsider it for backpatching now that we haven't seen
> side-effects.

Yeah, that's a no-go for us. I guess that's one more reason to upgrade.

Thanks Magnus,

Best regards,

depesz

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message vigneshwaran balaji 2016-05-25 11:20:50 Re: Postgres Help - Reg
Previous Message Magnus Hagander 2016-05-25 10:56:18 Re: Too high rate of progress information from pg_basebackup