Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executed query.
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2018-02-09T20:50:44Z
Lists: pgsql-hackers
On Wed, Feb 7, 2018 at 7:04 PM, Thomas Munro <thomas.munro@enterprisedb.com> wrote: > 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. Looks right. Committed, but I thought the comment was strange (forget about?) so I just left that out. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Clear stmt_timeout_active if we disable_all_timeouts.
- be42015fcc7f 11.0 landed
-
Rearm statement_timeout after each executed query.
- f8e5f156b30e 11.0 cited