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

From hubert depesz lubaczewski
Subject Re: Too high rate of progress information from pg_basebackup
Date
Msg-id 20160525105852.GA26536@depesz.com
Whole thread Raw
In response to Re: Too high rate of progress information from pg_basebackup  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Too high rate of progress information from pg_basebackup
List 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/

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Too high rate of progress information from pg_basebackup
Next
From: digoal@126.com
Date:
Subject: BUG #14159: PostgreSQL 9.6 parallel scan consume very high mutex lock