| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com, david(at)fetter(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Statement timeout behavior in extended queries |
| Date: | 2017-04-03 14:05:16 |
| Message-ID: | 12207.1491228316@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
>> * The difference is that the Execute message stops the statement_timeout timer,
> No. Parse, bind and Execute message indivually stops and starts the
> statement_timeout timer with the patch.
That seems like it could represent quite a lot of added overhead,
on machines where gettimeofday() is slow ... which is still a lot
of them, unfortunately.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-04-03 14:16:18 | Re: Variable substitution in psql backtick expansion |
| Previous Message | Tom Lane | 2017-04-03 13:59:03 | Re: delta relations in AFTER triggers |