| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Rukh Meski <rukh(dot)meski(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench throttling latency limit |
| Date: | 2014-08-27 17:05:25 |
| Message-ID: | alpine.DEB.2.10.1408271900570.28571@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> [...]
>
> Yeah, something like that. I don't think it would be necessary to set
> statement_timeout, you can inject that in your script or postgresql.conf if
> you want. I don't think aborting a transaction that's already started is
> necessary either. You could count it as LATE, but let it finish first.
I've implemented something along these simplified lines. The latency is
not limited as such, but slow (over the limit) queries are counted and
reported.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-limit-5.patch | text/x-diff | 13.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-08-27 17:07:13 | Re: postgresql latency & bgwriter not doing its job |
| Previous Message | Thomas Munro | 2014-08-27 17:00:17 | Re: SKIP LOCKED DATA (work in progress) |