Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executed query.

Поиск
Список
Период
Сортировка
От Thomas Munro
Тема Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executed query.
Дата
Msg-id CAEepm=3BdR_yB_WEkKGF0M180f6=f=4R4R6o6mWJL9e8vtj6wg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executedquery.  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executed query.
Список pgsql-hackers
On Tue, Feb 6, 2018 at 5:21 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 9/18/17 22:41, Andres Freund wrote:
>> Rearm statement_timeout after each executed query.
>
> This appears to have broken statement_timeout behavior in master such
> that only every second query is affected by it.

Yeah, I also just ran into this while testing a nearby complaint about
statement timeouts vs parallel query.  In the error path
stmt_timeout_active remains true, so the next statement does nothing
in enable_statement_timeout().  I think we just need to clear that
flag in the error path, right where we call disable_all_timeouts().
See attached.

-- 
Thomas Munro
http://www.enterprisedb.com

Вложения

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: PDF Builds on borka (Debian/stretch) broken - 9.6