| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| 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 15:13:29 |
| Message-ID: | 53FDF599.2060703@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/27/2014 06:08 PM, Fabien COELHO wrote:
>>> I've submitted this "simple" lag limit version because being able to
>>> measure quickly and simply (un)responsiveness seems like a good idea,
>>> especially given the current state of things.
>>
>> Ok, fair enough. I don't think doing a "latency limit" would be significantly
>> harder, but I can't force you. I'll mark this as Returned with Feedback then.
>
> Hmmm. I can distinguish just the two cases. Rather mark it as "waiting on
> author", I may give it a go.
Feel free to mark it as such if you think you can get a new version
posted in the next few days.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-08-27 15:24:53 | Re: [BUGS] Re: BUG #9555: pg_dump for tables with inheritance recreates the table with the wrong order of columns |
| Previous Message | Fabien COELHO | 2014-08-27 15:08:14 | Re: pgbench throttling latency limit |