Re: pgsql: Fix base backup rate limiting in presence of slow i/o

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Fix base backup rate limiting in presence of slow i/o
Date: 2016-12-21 20:20:04
Message-ID: CABUevEwR6Yo5G5tMoiuNrWfjZhZGk4TXfduk+pKeZFOZbSbw_w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Wed, Dec 21, 2016 at 6:55 PM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
wrote:

> On 19 December 2016 at 09:17, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> > Fix base backup rate limiting in presence of slow i/o
> >
> > Branch
> > ------
> > REL9_4_STABLE
>
> I'm seeing a warning on the 9.4 branch that looks to have been caused
> by this commit:
>
> basebackup.c: In function ‘throttle’:
> basebackup.c:1284:8: warning: variable ‘wait_result’ set but not used
> [-Wunused-but-set-variable]
> int wait_result;
>

Interesting.

ff44fba4 replaced the latch in walsender, which was not backported (of
course).

But it also added a CHECK_FOR_INTERRUPTS there.

9.4 does not have a CHECK_FOR_INTERRUPTS anywhere near there. Perhaps
what's really needed is to put one of those in regardless?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-12-21 22:39:57 pgsql: Fix detection of unfinished Unicode surrogate pair at end of str
Previous Message Tom Lane 2016-12-21 20:18:58 pgsql: Fix strange behavior (and possible crashes) in full text phrase