| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Hubert Lubaczewski <depesz(at)depesz(dot)com> |
| 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:56:18 |
| Message-ID: | CABUevEyr0HhkWxBo9G0aMgXUUD9ofgti8s=1jvFjwFyRs_ZPoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 25, 2016 at 12:54 PM, hubert depesz lubaczewski <
depesz(at)depesz(dot)com> wrote:
> On Wed, May 25, 2016 at 12:52:55PM +0200, Magnus Hagander wrote:
> > This was fixed in pg_basebackup in 9.4, see commit
> > 8198a321c9ea2072c5acde438f4d19638e04f6f2.
>
> Hmm .. - we can't upgrade to 9.4. Any chance to have this backported to
> 9.3? It doesn't look like new functionality, more like bugfix, to me.
>
>
IIRC that was discussed at the time and we decided not to.
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.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2016-05-25 10:58:52 | Re: Too high rate of progress information from pg_basebackup |
| Previous Message | hubert depesz lubaczewski | 2016-05-25 10:54:16 | Re: Too high rate of progress information from pg_basebackup |