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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Rearm statement_timeout after each executed query.
Date: 2018-02-06 04:21:44
Message-ID: 6a909374-2602-7136-8c70-397330a418f3@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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. For example:

create table t1 as select * from generate_series(0, 100000000) as _(a);
set statement_timeout = '1s';
explain analyze select from t1 where a = 55; -- gets canceled
explain analyze select from t1 where a = 55; -- completes (>1s)
explain analyze select from t1 where a = 55; -- gets canceled
explain analyze select from t1 where a = 55; -- completes (>1s)
etc.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2018-02-06 14:05:59 Re: pgsql: Support parallel btree index builds.
Previous Message Robert Haas 2018-02-05 22:34:05 pgsql: Fix possible crash in partition-wise join.

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-02-06 04:34:19 Re: Query running for very long time (server hanged) with parallel append
Previous Message Peter Geoghegan 2018-02-06 04:20:39 Re: [HACKERS] MERGE SQL Statement for PG11