Re: [COMMITTERS] pgsql: Fix base backup rate limiting in presence ofslow i/o

Поиск
Список
Период
Сортировка
От Dean Rasheed
Тема Re: [COMMITTERS] pgsql: Fix base backup rate limiting in presence ofslow i/o
Дата
Msg-id CAEZATCXwVctbNtbxi7ce2SmVb+nA61A764TNNoMpX=Mv8=LKMQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Fix base backup rate limiting in presence ofslow i/o  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: [COMMITTERS] pgsql: Fix base backup rate limiting in presence ofslow i/o  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-committers
On 21 December 2016 at 20:20, Magnus Hagander <magnus@hagander.net> wrote:
> On Wed, Dec 21, 2016 at 6:55 PM, Dean Rasheed <dean.a.rasheed@gmail.com>
>> 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?
>

Yeah, it seems reasonable that there should be a CHECK_FOR_INTERRUPTS() there.

I'm not really familiar with that code, but it looks like the signal
handler in 9.4 might not set that latch, so throttle() would have to
rely on setting ImmediateInterruptOK to make the sleep interruptable,
in which case the wait result would be irrelevant, right?

Regards,
Dean


В списке pgsql-committers по дате отправления:

Предыдущее
От: Michael Meskes
Дата:
Сообщение: [COMMITTERS] pgsql: Fix buffer overflow on particularly named files and clarifydocu
Следующее
От: Tom Lane
Дата:
Сообщение: [COMMITTERS] pgsql: Give a useful error message if uuid-ossp is built withoutprecon