| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Cc: | 'Tatsuo Ishii' <ishii(at)sraoss(dot)co(dot)jp>, "david(at)fetter(dot)org" <david(at)fetter(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement timeout behavior in extended queries |
| Date: | 2017-04-04 06:26:24 |
| Message-ID: | 20170404062624.b5o56k6oyr7bj3s6@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-04-04 06:18:04 +0000, Tsunakawa, Takayuki wrote:
> From: Tatsuo Ishii [mailto:ishii(at)sraoss(dot)co(dot)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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-04-04 06:30:40 | Re: ANALYZE command progress checker |
| Previous Message | Andres Freund | 2017-04-04 06:20:50 | Re: Supporting huge pages on Windows |