Horton

Re: Statement timeout behavior in extended queries

Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>

View thread View on postgr.es
From: "Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>
To: 'Tatsuo Ishii' <ishii@sraoss.co.jp>
Cc: "david@fetter.org" <david@fetter.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-04-04T06:18:04Z
Lists: pgsql-hackers 
From: Tatsuo Ishii [mailto:ishii@sraoss.co.jp]
> It's too late. Someone has already moved the patch to the next CF (for
> PostgreSQL 11).

Yes, but this patch will be necessary by the final release of PG 10 if the libpq batch/pipelining is committed in PG 10.

I marked this as ready for committer in the next CF, so that some committer can pick up this patch and consider putting it in PG 10.  If you decide to modify the patch, please change the status.

Regards
Takayuki Tsunakawa

Commits

  1. Rearm statement_timeout after each executed query.