Re: Statement timeout behavior in extended queries - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Statement timeout behavior in extended queries
Date
Msg-id 5692.1491399991@sss.pgh.pa.us
Whole thread Raw
In response to Re: Statement timeout behavior in extended queries  ('Andres Freund' <andres@anarazel.de>)
Responses Re: Statement timeout behavior in extended queries  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2017-04-05 00:39:51 -0400, Tom Lane wrote:
>> but
>> if that's what we're doing, let's make sure we do it consistently.
>> I haven't read the patch, but the comments in this thread make me fear
>> that it's introducing some ad-hoc, inconsistent behavior.

> I'm a bit worried too due to the time constraints here, but I think
> resetting the clock at Execute too actually makes a fair amount sense.

Meh.  Two days before feature freeze is not the time to be introducing
a rushed redefinition of the wire protocol --- and let's not fool
ourselves, that is what this amounts to.  Let's push this out to v11
and think about it more carefully.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: partitioned tables and contrib/sepgsql
Next
From: Robert Haas
Date:
Subject: Re: partitioned tables and contrib/sepgsql