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

From Andres Freund
Subject Re: Statement timeout behavior in extended queries
Date
Msg-id 20170404062624.b5o56k6oyr7bj3s6@alap3.anarazel.de
Whole thread Raw
In response to Re: Statement timeout behavior in extended queries  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
Responses Re: Statement timeout behavior in extended queries  ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>)
List pgsql-hackers
On 2017-04-04 06:18:04 +0000, Tsunakawa, Takayuki wrote:
> 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
puttingit in PG 10.  If you decide to modify the patch, please change the status.
 

Given the concern raised in http://archives.postgresql.org/message-id/12207.1491228316%40sss.pgh.pa.us
I don't see this being ready for committer.

- Andres



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Supporting huge pages on Windows
Next
From: Masahiko Sawada
Date:
Subject: Re: ANALYZE command progress checker