From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executed query. |
Date: | 2018-02-14 18:35:08 |
Message-ID: | 20180214183508.vvvm6h7swt34i4km@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2018-02-09 15:50:44 -0500, Robert Haas wrote:
> On Wed, Feb 7, 2018 at 7:04 PM, Thomas Munro
> <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> > On Tue, Feb 6, 2018 at 5:21 PM, Peter Eisentraut
> > <peter(dot)eisentraut(at)2ndquadrant(dot)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.
>
> Looks right. Committed, but I thought the comment was strange (forget
> about?) so I just left that out.
Thanks Peter, Thomas, Robert!
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-02-14 19:47:42 | pgsql: Fix broken logic for reporting PL/Python function names in errco |
Previous Message | Tom Lane | 2018-02-14 03:15:24 | pgsql: Support CONSTANT/NOT NULL/initial value for plpgsql composite va |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-02-14 18:56:51 | Re: Cancelling parallel query leads to segfault |
Previous Message | Andres Freund | 2018-02-14 18:17:10 | Re: JIT compiling with LLVM v10.1 |