Horton

Re: Statement timeout behavior in extended queries

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: 'Andres Freund' <andres@anarazel.de>
To: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
Cc: Tatsuo Ishii <ishii@sraoss.co.jp>, "david@fetter.org" <david@fetter.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-04-04T23:56:26Z
Lists: pgsql-hackers 
On 2017-04-04 23:52:28 +0000, Tsunakawa, Takayuki wrote:
> From: Andres Freund [mailto:andres@anarazel.de]
> > Looks to me like npgsql doesn't do that either.  None of libpq, pgjdbs and
> > npgsql doing it seems like some evidence that it's ok.
> 
> And psqlODBC now uses always libpq.
> 
> Now time for final decision?

I'll send an updated patch in a bit, and then will wait till tomorrow to
push. Giving others a chance to chime in seems fair.

- Andres

Commits

  1. Rearm statement_timeout after each executed query.